Docs
Open dashboard
Developers

API keys

Keys are per workspace. Create one per integration so each can be revoked on its own, and keep every key out of the browser.

Create, use, rotate, revoke

  1. Create

    Under Configuration → General → API Keys, press Create API Key and give it a Key name after the system that will use it, for example "Zapier integration". Creating keys needs the Edit Settings permission and a plan with API & MCP access; on a plan without it the button refuses with a message naming the feature.

  2. Copy it now

    The Copy your API key dialog shows the full key once. It looks like inspra_live_ followed by 32 characters. Store it as a secret in the system that calls the API; the dashboard keeps only a hash and can never show it again.

  3. Read the list

    Each key is listed by name with its prefix and the rest masked, when it was created, and when it was last used (or Never used). Last used updates when the key authenticates against the API or the MCP server, at most once every five minutes. Revoked keys stay in the list, dimmed, with a Revoked badge.

  4. Rotate

    Create a new key, move the integration to it, confirm the new key's last-used time updates, then revoke the old one.

  5. Revoke

    The bin icon (Revoke key) asks for confirmation and warns that any integration using the key stops working immediately. Revocation cannot be undone.

Never put a key in a browser or mobile app. For browser calls, create the session on your server with Create web call.

Base URL

Send requests to https://api.inspra.ai/v1 with the key as a bearer token: Authorization: Bearer <your key>. On your own domain, use https://<your domain>/v1.

Limits

LimitValue
Requests120 requests in a sliding 60-second window per workspace by default, shared by every key the workspace has and by the MCP server. A plan can set its own figure. Over the limit, requests get 429 rate_limited with a Retry-After header in seconds.
Page sizeUp to 100 items per page, 20 by default.
CreditsRequests that place calls, start or resume campaigns or create web calls are refused with 403 forbidden when the workspace cannot fund the next billable unit, has a negative balance, or has reached its monthly conversation limit. Reads, pause and terminate still work.
Plan accessThe API and MCP need a plan with API & MCP access (Growth and above). Campaign endpoints also need the Campaigns feature.
ScopeA key resolves to exactly one workspace and carries the workspace's full access; there are no per-key scopes.
RetentionCalls older than the workspace's call-history retention are not returned.

Concurrency of live calls is a plan limit enforced when campaigns run, not a per-request limit. See client subscription plans.

Go to workspace