$ curl https://api.integrable.cloud/api/bots \ -H "Authorization: Bearer $INTEGRABLE_API_KEY" \ -H "Idempotency-Key: $(uuidgen)"
{
"items": [{
"id": "0199f2c4-…",
"name": "Front desk",
"status": "active",
"total_conversations": 1284
}],
"has_more": false
}- Documented operations
- 188
- Endpoints
- 159
- Official SDKs
- 2
- API version — dated, and pinnable
- 2026-09-03
Install a client
Two SDKs, generated from the spec
$ npm install @integrable-cloud/sdk$ pip install integrable-cloudThe platform
Everything the dashboard does, as an endpoint
REST API
188 operations across 159 endpoints, with a committed OpenAPI document you can generate a client from.
/docs/api
SDKs
Official TypeScript and Python clients, generated from the same OpenAPI document the reference is built from.
/developers/sdks
MCP server
Point Claude, ChatGPT or your editor at your workspace and let it read and change things directly.
/developers/mcp
Webhooks
Signed events for leads, conversations and bookings, so anything with an endpoint can be a destination.
/docs/webhooks
Rate limits
Published per-endpoint limits, with a Retry-After header on every 429 rather than a guess.
/developers/limits
Conventions
Idempotency, pagination and a dated API version — currently 2026-09-03 — with deprecations arriving as response headers.
/docs/conventions
Webhooks
React to events instead of polling for them
Leads, handovers, conversations and indexing events, delivered signed with a timestamp — retried when your endpoint fails, replayable from the log.
- HMAC-SHA256 signature on every delivery
- A test fire before you rely on it
- One-click replay of a failed delivery
MCP server
Ask your AI assistant about your workspace
Connect Claude, ChatGPT or your editor to your workspace over MCP and ask what visitors wanted this week — or add a document to the knowledge base.
- Nine task-shaped tools
- Scoped by your API key
- One write: add knowledge
Conventions
Three things that hold on every endpoint
Retries are safe
Every write takes an idempotency key, so a retry is never a duplicate.
Errors explain themselves
RFC 9457 problem details, each linking to a page for that code.
Versions are dates
Pin 2026-09-03 and response shapes never change under you.
Developer questions
Still deciding?Ask the people who build it.Is the reference generated or hand-written?
Generated, from the same OpenAPI document the SDKs are built from — and CI fails the build if the two drift.How are errors returned?
As RFC 9457 problem details, each with a machine-readable code and a type URI that resolves to a page explaining that exact error.Are writes safe to retry?
Yes. Every write accepts an Idempotency-Key header, so retrying after a timeout returns the original result instead of creating a duplicate.How is the API versioned?
By date, currently 2026-09-03. Pin a version with a header and response shapes are fixed to that date; deprecations arrive as response headers.
