HTTP API & SDKs

Every deployed app exposes the same surface — this uniformity is why every external system integrates the same way.

Need	Endpoint
Auth	POST /api/auth/login → { accessToken }
Send an event	POST /api/pulse/x/<app>/in
Read results	GET /api/pulse/events/<topic>
Live stream	GET /api/pulse/events/stream (SSE)
Request/response	SDK duplex() — correlated WebSocket

All endpoints take Authorization: Bearer <accessToken>. Note the login response field is accessToken — not token.

SDKs

JavaScript · Python (pulse-py) · Rust · Go · Java. The Python duplex() example:

from pulse import Client
async with Client(...).duplex() as d:
    reply = await d.send({"severity": "error", "msg": "hi"})

Orchestrator bridges

Worked, end-to-end-tested bridge examples exist for 14 orchestrators: n8n, Node-RED, LangGraph, Temporal, Prefect, Dagster, Kestra, Airflow, Apache Camel, Spring Integration, AWS Step Functions, Google Cloud Workflows, Azure Durable Functions and Azure Logic Apps — each a thin client of the surface above. See Call your app from anywhere for the pattern.