API reference · Dashboard
Create API key
Creates a key. The plaintext is returned exactly once and never again - only a peppered hash is stored.
- Authentication
- Bearer token
- Retries
- Idempotency-Key
- Body
- application/json
- Version
- 2026-09-03
Headers
Idempotency-KeystringA unique key of your choosing, so this request can be retried safely. The first request with a given key executes; every replay returns that first response unchanged, with
Idempotent-Replay: trueset.Generate one key per action, not per session - reusing a key with a different body is refused with 422 rather than silently replaying the wrong answer. Keys are remembered for 24 hours. A request that failed releases its key, so a retry after fixing the payload runs normally.
Up to 255 characters
Request body
application/json · required
object
Responses
- 201Createdapplication/json
object
5 response headers
- RateLimit-Limit
Requests permitted in the current window.
- RateLimit-Remaining
Requests left in the current window. Back off before it reaches 0.
- RateLimit-Reset
Seconds until the current window resets.
- X-API-Version
The dated version of the API contract that served this response, e.g.
2026-09-03. Pin against it; it changes only when a response shape changes incompatibly.- X-Request-ID
Quote this in a support request to identify the call.
- 422Validation error
The shared error envelope, served as
application/problem+jsonwitherror.codeset to validation_error. Its details name each field that failed and why.
Example request
curl -X POST "https://api.integrable.cloud/api/api-keys" \
-H "Authorization: Bearer $INTEGRABLE_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{}'Set INTEGRABLE_API_KEY first. The same call from the TypeScript or Python SDK takes the same fields.
Errors
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.idempotency_key_reused· 422 — This `Idempotency-Key` was used before, for a request with a different body.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-bot limit on top.
More Dashboard endpoints
- get/api/api-keysList API keys
- delete/api/api-keys/{api_key_id}Revoke API key
- get/api/bots/{bot_id}/analyticsBot analytics
- get/api/bots/{bot_id}/analytics/gapsKnowledge gaps
- get/api/bots/{bot_id}/analytics/insightsBot insights
- get/api/bots/{bot_id}/contactsList contacts
- get/api/bots/{bot_id}/contacts/exportExport contacts
- get/api/bots/{bot_id}/contacts/{contact_id}/dataExport subject data
- delete/api/bots/{bot_id}/contacts/{contact_id}/dataErase subject data
- get/api/bots/{bot_id}/conversationsList conversations
- post/api/bots/{bot_id}/conversations/bulkBulk update conversations
- get/api/bots/{bot_id}/conversations/{conversation_id}Get conversation
- get/api/logsList request logs
- get/api/logs/summaryRequest log summary
- get/api/overviewOrg overview
- get/api/usagePlan usage
- get/api/viewsList saved views
- post/api/viewsCreate saved view
- patch/api/views/{view_id}Update saved view
- delete/api/views/{view_id}Delete saved view
Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.