Joinblink Blink API
Official vendor OpenAPI document · agent-readyCommunicationsChat Messagingbearer14 EndpointsREST
For Agents
Send targeted feed events to Blink users or groups, archive and update past events, retrieve form submissions, and manage user-linked accounts so agents can broadcast company comms or pull frontline data into other tools.
Use for: I need to send a company-wide announcement to all Blink users, Post a feed event to the 'Warehouse Staff' group with a shift update, Archive yesterday's feed event about the cancelled town hall, Find the Blink feed event ID for our external announcement-2026-06-01 reference
Not supported: Does not handle direct user-to-user chat messaging, voice or video calls, or payroll data - use for company feed events, form submissions, and linked-account management only.
Blink is an employee-experience platform built for frontline and deskless workers, combining a company feed, forms, and integrations with HR systems. The API lets developers push targeted feed events to users or groups, archive or update those events, retrieve form responses, and manage the linked third-party accounts each user is connected to. It is the right tool when an internal system needs to surface notifications or collect form data inside the Blink mobile app.
Install Jentic One Beta
Connect the Blink API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blink API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjoinblink.com%2Fjoinblink" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjoinblink.com%2Fjoinblink" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Blink API.
Send a targeted feed event to a list of users, groups, or external IDs
Update or archive an existing feed event when content changes or expires
Look up a feed event ID by the external identifier supplied at create time
Pull form submissions from Blink to feed downstream HR or operations systems
Retrieve user data with filters to map Blink users to internal records
Connect or remove a user's linked third-party account from Blink
Use Cases
Patterns agents use Blink API for, with concrete tasks.
★ Push HR announcements to frontline workers
Internal communications and HR teams can push targeted feed events to deskless employees by group, role, or external ID. The API accepts a structured event payload, routes it to the Blink mobile feed, and returns an event ID that can later be updated or archived. This replaces manual posting in the Blink admin UI when announcements are generated by an upstream HRIS workflow.
Call POST /feed/events with audience 'Warehouse Staff' and body 'Shift change effective Monday' to publish the announcement to that group's Blink feed
Sync form submissions to a data warehouse
Operations teams running checklists, audits, or feedback forms in Blink can pull responses through the API for analytics. GET /forms lists available forms, and GET /forms/{id}/submissions returns the structured response payload for downstream pipelines. Combine this with a scheduled job to land Blink form data in BigQuery, Snowflake, or a similar warehouse.
Call GET /forms to list active forms, then GET /forms/{id}/submissions for the 'Weekly Safety Check' form to retrieve responses for ETL into a warehouse
Correct or retract a published announcement
When a company-wide post needs editing or pulling, the API supports both in-place updates and full archival. PUT /feed/events/{event_id} replaces the event content, and POST /feed/events/{event_id}/archive removes it from active feeds. Per-user archival via the user-scoped archive endpoint allows targeted retraction without affecting other recipients.
Call PUT /feed/events/{event_id} with corrected body text, or POST /feed/events/{event_id}/archive to remove a mistakenly published event
Agent-driven internal comms via Jentic
An AI assistant integrated with Slack or Teams can be asked to broadcast a message to frontline staff and use Jentic to call Blink without storing the bearer token in the agent. The agent expresses intent, Jentic resolves it to POST /feed/events, injects the credential, and confirms delivery. This is useful for HR Copilots that orchestrate multi-channel comms.
Use Jentic to search 'send a Blink feed event', load POST /feed/events, and execute it with the message 'Heatwave protocol active - see latest safety guidance'
Key Endpoints
14 endpoints — blink is an employee-experience platform built for frontline and deskless workers, combining a company feed, forms, and integrations with hr systems.
METHOD
PATH
DESCRIPTION
POST
/feed/events
Send a feed event to users or groups
PUT
/feed/events/{event_id}
Update an existing feed event
POST
/feed/events/{event_id}/archive
Archive a feed event
GET
/feed/event-by-external-id
Look up event by external identifier
GET
/user
Retrieve user data with filters
GET
/forms/{id}/submissions
Retrieve form responses
POST
/user/{user_id}/linked-accounts
Link an integration account to a user
GET
/linked-accounts
List all linked accounts
POST
/feed/events
Send a feed event to users or groups
PUT
/feed/events/{event_id}
Update an existing feed event
POST
/feed/events/{event_id}/archive
Archive a feed event
GET
/feed/event-by-external-id
Look up event by external identifier
GET
/user
Retrieve user data with filters
GET
/forms/{id}/submissions
Retrieve form responses
POST
/user/{user_id}/linked-accounts
Link an integration account to a user
GET
/linked-accounts
List all linked accounts
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Blink API by hand means learning its bearer auth, formatting feed-event payloads, and tracking event and linked-account ids yourself. Through Jentic you install once, import the Blink API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Blink puts the event id in the URL path (/feed/events/{event_id}), so a rule can pin your agent to one feed event: it can update or archive that event and nothing else. You choose the operations it may call, so ones like adding linked accounts are not included unless you add them.
Credential isolation
Your Blink bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a Blink announcement' or 'get form submissions', and Jentic returns the matching Blink operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Blink API through Jentic.
What authentication does the Blink API use?
The Blink API uses HTTP bearer authentication - every request must carry an Authorization: Bearer {token} header. Jentic stores the token encrypted and injects it on each call, so agents never see the raw bearer value in their prompt context.
Can I send a targeted feed event to a specific group of users?
Yes. POST /feed/events accepts an audience definition that can include user IDs, external IDs, or group identifiers, so a single call can target a department, location, or role without iterating per user.
What are the rate limits for the Blink API?
The Blink spec does not publish numeric rate limits. Treat feed event creation as a moderate-volume endpoint and watch for HTTP 429 responses; refer to developer.joinblink.com for the latest documented thresholds before running large broadcast jobs.
How do I retrieve form submissions through Jentic?
Search Jentic for 'list Blink form submissions', load GET /forms/{id}/submissions, and execute it with the form ID. Jentic returns the structured response array. Get started with Jentic One, the self-hosted execution layer.
Can the Blink API archive a post for one user only?
Yes. POST /feed/events/{event_id}/user/{user_id}/archive archives the feed event for a single user without affecting how it appears for other recipients - useful for targeted retraction or per-user clean-up.
How do I link a third-party account to a Blink user?
Call POST /user/{user_id}/linked-accounts with the integration details to attach the account, GET /user/{user_id}/linked-accounts to list them, and DELETE /user/{user_id}/linked-account/{linked_account_id} to remove a stale link when an employee leaves.
Can I limit what my agent is allowed to do with the Blink API?
Yes. With your self-hosted Jentic One instance, your own rules decide which Blink operations and credentials the agent may use, so you pick exactly what it can call. Because Blink puts the event id in the URL path (/feed/events/{event_id}), a rule can pin the agent to one feed event, letting it update or archive that single event and nothing else. Operations you do not grant, such as adding linked accounts via POST /user/{user_id}/linked-accounts, stay off-limits until you explicitly allow them.
GET STARTED