Skip to main content
The notable changes to Ringup’s API, tools, and docs. The request and response shapes are versioned in the base path (/v1): within a version, changes are additive, and a breaking change ships under a new version. See the stability note in the API introduction.
July 2026
Interactive docs

Interactive API reference, errors, and language tabs

  • A live playground on every tool in the API reference: call the sandbox from the page.
  • A new Errors page that separates transport errors (4xx/5xx) from payment outcomes (a decline is a 200 with status: failed, not an HTTP error).
  • curl, Node, and Python tabs on the Quickstart.
  • A rendered flow diagram on How it works, and a “Next steps” trail on every page.
July 2026
Identity

Recognize at the start of the call

  • identify is documented and wired to run at the greeting, not at the payment moment, so a returning caller is greeted by name and never re-asked for anything recognition already knows. See Caller Identity.
  • Caller and merchant identity are now two concepts: who is paying (Caller Identity) and which business they reached (Merchant Identity).
  • The Checkout Session is the object every payment turns on: create_checkout returns payment_required as required, optional, or none. See Checkout Session.
June 2026
Integrations

Eight platforms and a keyless sandbox

  • Integration guides for Vapi (native handoff and call transfer), Retell, ElevenLabs, Deepgram, LiveKit, OpenAI Realtime, Pipecat, and Twilio ConversationRelay.
  • A shared test sandbox that is live for every account from the first command, with ready-made merchants and a recognized caller. No keys to mint. See Testing.
  • Charges settle on each merchant’s own payment processor: Ringup never becomes the merchant of record and never holds the money.