Skip to content
cleo.Developers
Build reliably/Limits
Cleo documentation

Limits

Keep call tasks bounded and leave room for API rate limits.

Content reviewed · Maintained by Cleo Powered · Report a documentation issue · Verification basis

Task limits

Input
Destination
Accepted range
E.164 format, 8–15 digits after the + prefix, without spaces or punctuation.
Input
Objective
Accepted range
1–4,000 characters.
Input
Protected context
Accepted range
Up to 20 named strings, 1–2,000 characters each; combined UTF-8 value bytes at most 16 KiB. Names match [a-z][a-z0-9_]{0,63}.
Input
Constraints / success criteria
Accepted range
Up to 50 strings each, at most 500 characters per string.
Input
Requested duration
Accepted range
30–3,600 seconds; default 300. Workspace, assistant, or calling-service limits may be lower.
Input
Idempotency key
Accepted range
Non-empty, up to 200 characters.

The calling service also caps serialized call context at 16 KiB, including task instructions, context, schema, and caller identity. Keep these inputs concise; satisfying each field’s individual limit does not guarantee the combined task fits.

A requested call-duration limit is separate from an HTTP client timeout. Timing out a request or closing a polling process does not cancel an active call.

Request rate limits

The gateway defaults to 120 requests per minute per API key and 600 authentication attempts per minute per client IP. Deployment settings can change these limits. Call-frequency and destination limits can apply separately.

On 429 rate_limit_exceeded, honor the Retry-After header. Poll one active call every few seconds and stop at a terminal state. Account for all active calls when choosing a polling interval.

Account availability

Public API calls use the owning workspace’s assistant, permissions, and usage availability. Check the platform for current account and billing details. Passing input validation does not guarantee that a call is eligible to start.

Documentation
Get an API key

Explore the docs

IntroductionSubmit a phone errand, follow the call, and inspect its outcome.Bot account onboardingRegister from Muse or another bot, verify your phone, receive an API key, and set your dashboard password by email.API overviewWhich endpoints are available, how they authenticate, and what is supported today.Make your first callCall your own phone, refresh its status, and inspect the returned call data.AuthenticationCreate a key in Cleo and authenticate requests with a bearer token.Create a callQueue one bounded phone task and receive durable task and call IDs.Get a callRead the most recently saved state of a call.Sync a callRefresh a call from the calling service and retrieve its latest saved state.Cancel a callCancel queued work or request a stop, then follow confirmation.The call objectThe shared response returned by create, get, sync, and cancel.Health checksCheck API liveness and readiness without an API key or placing a call.Results & schemasUnderstand result_schema, returned metadata, and what result_schema_valid does and does not establish.Task and call lifecycleFollow a call from acceptance to its final outcome.Idempotency & retriesRecover from an interrupted request without accidentally placing a second call.Safety & permissionsHow Cleo evaluates a call task before it can dial.Errors & troubleshootingUnderstand API errors and choose a safe next step.LimitsKeep call tasks bounded and leave room for API rate limits.Verification & limitationsReproduce our public health and schema checks and understand what has not been tested.Bot integrationsChoose a route for connecting your assistant to Cleo's public API.ChatGPTConfigure a private GPT Action with Cleo OpenAPI and bearer authentication.ClaudeConnect Claude client tools or a Claude Code shell workflow.Grok & Grok BotConnect xAI function tools and check Grok Bot execution requirements.OpenClawInstall a local skill for an approved Cleo calling workflow.GeminiMap Gemini function declarations to Cleo REST operations.Copilot StudioAdd Cleo through a REST API tool, custom connector, or flow.n8nBuild an authenticated HTTP workflow with durable call recovery.ZapierBuild a private Zapier integration for approved Cleo calls.