Callerino

API & MCP

Use your own account, agents and systems. Contacts, campaigns, agents and appointments share the same permissions and safeguards as the application. Start with callerino_capabilities: documented tools may be unavailable for your account or while a feature awaits activation. A tool in this catalogue does not prove that its feature is live.

OpenAPI 3.1 · version 1.0.1 · OAuth discovery · Account settings

Authentication and permissions

OAuth uses the existing hosted login with PKCE. Your client must have an explicitly registered redirect URI. API keys need explicit management:read, management:write or management:execute scopes. Old call-only keys gain no new permissions. Never paste a token into a prompt.

First request

POST /api/v1/actions/callerino_contacts_list
Authorization: Bearer $CALLERINO_TOKEN
Content-Type: application/json

{"limit":20}

Follow nextCursor until null, including after an empty filtered page. Contact cursors expire after 15 minutes and bind the account, action and filters. Exports are paged live reads, not an immutable whole-account snapshot.

Safe changes and recovery

Read the current version/revision. Reuse the same operationId and identical input after a timeout; read callerino_contact_operation_get or the campaign batch receipt first. A conflict means reread and review. Removing a contact is reversible; restore does not reinstate call approval. Imports add new contacts only.

Save → prepare → show exact recipients, time, agent, callback scope and possible cost → obtain explicit human approval → execute unchanged. A model-generated approval flag is not human consent. Pause blocks future start authorization and does not hang up an active call. pending_verification is not a confirmed booking. Opt-outs, grants, billing and provider limits always apply.

MCP installation

Endpoint: https://mcp.callerino.de/mcp. OAuth authorization opens in the browser. Register your client's exact callback; other customers use their own account. Configuration, registration and successful read-only authentication must be verified before use.

Installation prompt

Configure the Callerino MCP at https://mcp.callerino.de/mcp using OAuth Authorization Code with PKCE. Read its protected-resource metadata. Use a registered public client and exact callback for my MCP client; if registration is needed, explain that step. Open the legitimate hosted OAuth login so I can sign in myself. Never ask me to paste tokens or put credentials in this prompt. After login, call callerino_capabilities and list my contacts read-only. Do not create contacts, calls, bookings or costs. Report the verified account-access result and any missing scope.

API operations

Find an operation

Loading specification…

Errors

400 invalid request · 401 authenticate again · 403 check scope/account rights · 404 owned object absent · 409 reread/review · 429 wait · 503 reconcile the existing receipt before retrying a side effect.