mocop
Browse · Docs · Guide · Analyze

Rindee API

API by Rindee · rest

The Rindee API lets you provision and operate AI phone agents, manage contacts and campaigns, schedule appointments, and receive real-time call events over webhooks. Authentication All requests authenticate with a Bearer API key: Authorization: Bearer rk_live_... Create and manage keys under API keys (/v1/api-keys). Keys are capability-scoped (operate, settings, api_keys, webhooks) and a key can never exceed the capabilities of the member that minted it. Resellers A reseller account runs other businesses — its tenants — entirely through the API. Reseller access is enabled by the Rindee team; on any other account the Tenants endpoints answer 403 not_a_reseller. Create a tenant with POST /v1/tenants, then act inside it by sending your own key with its id in the X-Tenant-Id header: Authorization: Bearer rk_live_... X-Tenant-Id: 5f0c...-tenant-id With the header, every endpoint in this reference — agents, phone numbers,…

Verification: observed. Source: crawl.

Capabilities (508)

  • Inbound Auth
  • Inbound Worker
  • Ps Aors Noop
  • Ps Aors Multi
  • Ps Aors Noop
  • Ps Aors Single
  • Ps Aors Noop
  • Ps Aors Noop
  • Ps Auths Noop
  • Ps Auths Multi
  • Ps Auths Noop
  • Ps Auths Single
  • Ps Auths Noop
  • Ps Auths Noop
  • Ps Endpoints Noop
  • Ps Endpoints Multi
  • Ps Endpoints Noop
  • Ps Endpoints Single
  • Ps Endpoints Noop
  • Ps Endpoints Noop
  • Websocket Clients Noop
  • Websocket Clients Multi
  • Websocket Clients Noop
  • Websocket Clients Single
  • Websocket Clients Noop
About · Contact · Privacy