Developer toolkit

Where things are

• Settings → API & webhooks: the API base URL, your plan's API limits, API keys (create with scopes and expiry, see last use, revoke) and outbound webhook endpoints (add, edit, test, rotate secret, delivery log). Owners and admins manage them; other members can see them read-only.
• Settings → Developer: the webhook trigger URL format, /api/triggers/webhook/<workflow id>, and your workspace ID for support tickets.
• API reference: /docs/api, and the OpenAPI 3.1 file at /api/v1/openapi.json.
• Building an app other workspaces can install? Register it in the developer portal (/developer-portal) — see Building a third-party app (OAuth) in the API reference.

SDKs

There are no official SDKs yet. The API is plain JSON over HTTPS, so any HTTP client works (see the curl, JavaScript and Python examples in the API reference), and you can generate a typed client from /api/v1/openapi.json with a tool such as openapi-generator or openapi-typescript.

Sending events to your systems

Subscribe an https endpoint to run.succeeded, run.failed, run.paused, review.decided and other events in Settings → API & webhooks (see REST API → Outbound webhooks). To send data from a specific point inside a workflow instead, add an HTTP Request, Webhook Call or Publish Output step there.