Documentation
Everything to integrate with adaptlive — REST API, outbound webhooks, and the Zapier app. Three composable surfaces over the same schema-of-record. Pick one to start, mix as you grow.
Quickstart
Mint an API key, make your first request, and subscribe to a webhook in under five minutes.
Read docsREST API
Bearer-token auth with READ / WRITE / ADMIN scopes. Cursor-paginated lists, idempotent writes, JSON envelopes, full OpenAPI 3.1 spec.
Read docsZapier app
14 user-facing triggers, 5 create/update actions, and 2 search actions backed by the local Zapier app package. Available by invite while it is not public in Zapier's directory.
Read docsIntegration patterns
How REST + outbound webhooks + Zapier compose. Security guidance, decision tables, and common combinations.
Read docsBase URL
https://adaptlive.app/api/v1Every request is authenticated. The machine-readable contract lives at /openapi.json — feed it into openapi-typescript, openapi-fetch, Stoplight, Postman, Insomnia, or any other OpenAPI tool to generate a typed client in one command. The dynamic equivalent at /api/v1/openapi.json always reflects the deployed shape.
Pick a surface
Three ways to wire adaptlive into the rest of your stack. They aren't mutually exclusive — most production integrations use at least two.
| Surface | Shape | Best for |
|---|---|---|
| REST API | HTTPS + Bearer ApiKey | On-demand reads / writes from your backend. |
| Outbound webhooks | HMAC-signed event POSTs | Reacting to events as they happen. |
| Zapier app | Triggers + actions on top of REST + webhooks | Wiring adaptlive into other SaaS without writing code. |
Ready to start?
The quickstart walks through authentication, making your first API call, and subscribing to a webhook.