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.