Joinblink Blink API

Name: Blink API
Brand: Blink API
Availability: InStock

✓ Official Vendor SpecCommunicationsChat 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.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with Blink API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Blink bearer tokens are stored encrypted in the Jentic vault. The Authorization header is injected at execution time, so the token never enters the agent's prompt, log, or conversation history.

Intent-based discovery

Agents search Jentic with phrases like 'send a Blink announcement' or 'get form submissions' and Jentic returns the matching Blink operation with its input schema, removing the need to consult developer.joinblink.com.

Time to first call

Direct Blink integration: 1-3 days to handle bearer auth, audience targeting, and error retries. Through Jentic: under 1 hour — search, load schema, execute.

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. Sign up at https://app.jentic.com/sign-up.

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.

Joinblink Blink API

Connect the Blink API to your agent

Capabilities

Start building with Blink API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs