mocop
Browse · Docs · Guide · Analyze

Cadence API

API by Cadence · rest

Every path here is generated from the live route table, and request and response schemas are generated from the validators that actually run — so this file cannot describe a route that does not exist, or a body the server would reject. Three things that catch people 1. Casing is not uniform. Brand routes are snake_case; conversation routes are camelCase. PATCH /v1/brands/{id} rejects camelCase rather than silently ignoring it. 2. Two different things are called a webhook. POST /v1/webhooks registers an endpoint *we* POST your inbound activity to — that is the one you want. PUT /v1/agents/{id}/webhook points *Google* somewhere other than Cadence and switches off flow handling. See the Delivery webhooks and Google inbound routing tags. 3. Three operations are irreversible and marked x-irreversible. They refuse with 409 CONFIRMATION_REQUIRED and change nothing until re-sent with {"confirm": "irreversible"}. Sandbox keys simulate delivery, so nothing…

Endpoint: https://api.cadencercs.com/

Verification: observed. Source: crawl.

Capabilities (92)

  • Approve a change from the current address
  • Confirm the new address
  • Sign in
  • Sign out
  • Request a password reset
  • Set a new password
  • Resend the verification email
  • Create a dashboard account (human path)
  • Verify an email address
  • Agent detail
  • Delete an agent that never reached Google
  • Delivery health
  • Archive an agent
  • List supporting documents
  • Upload a supporting document
  • Remove a supporting document
  • Carrier launch submission (draft and status)
  • Submit the agent for carrier launch
  • Save the carrier launch submission draft
  • Register this agent for carrier launch
  • One-tap opt-in link
  • The agent's profile at Google
  • Update the agent's profile at Google
  • Poll per-carrier launch state
  • Record launch-questionnaire answers
About · Contact · Privacy