Client Endpoints
Two endpoints serve the platform's own clients rather than integrations: the bridge, through which a workflow reaches the owner's own machine, and the web app's activity beacon. They are listed here so the API reference is complete; you rarely call them yourself.
Strongly Bridge
A Client Node in a workflow runs a task on the workflow owner's own computer, through the Strongly Bridge app running there (the client worker). The worker keeps a connection to the platform; the node calls the bridge as the workflow's owner, and the call ends when the worker answers.
GET /api/v1/bridge/status
Whether your client worker is connected now.
Response 200 OK: { connected: false, nodes: [] }, or when it is connected
{ connected: true, nodes, agent, capabilities }: the client nodes it can run, its version and
what it can do.
POST /api/v1/bridge/invoke
Run a client node on your machine and wait for its result. There is no time limit: the call ends when the worker answers, its connection is lost, or you stop waiting (cancelling the run).
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
node | string | Yes | The client node type |
inputs | object | No | Its inputs |
Response 200 OK: the node's result. A node that failed answers 200 with ok: false and
its error, so the workflow decides what to do.
| Status | When |
|---|---|
409 no-client-worker | No client worker is connected for you |
422 unsupported-client-node | Your worker does not run that node |
Activity beacon
POST /api/v1/telemetry/events
The web app's batch of activity events (pages visited, features used, page timings), sent with
navigator.sendBeacon so events of a page being left still arrive. It takes the signed-in
session only (no API key); the user and organization come from the session.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
events | array | Yes | 1 to 100 events: each with eventType, route, and as they apply referrerRoute, dwellTimeMs, featureName, action, component, lcpMs, fidMs, cls, traceId, spanId, timestamp |
Response 201 Created: { inserted }, how many events were recorded.