Ringflow
Documentation

Build with Ringflow.

Guides, API reference, and SDKs for Cloud Phone, the AI Contact Center, and the AI Sales Platform — everything you need to ship voice, SMS, and CRM workflows.

SLA-Backed API·OAuth 2.0 + Token·HMAC-Signed Webhooks·Enterprise Security·BAA Available
Popular guides

The six pages every team reads first.

  1. 01

    Port your existing number to Ringflow

    Step-by-step LOA, carrier validation, and porting timeline.

  2. 02

    Build an IVR with conditional routing

    Time-of-day rules, skills-based routing, and overflow agents.

  3. 03

    Connect HubSpot for click-to-call + sync

    Native marketplace install. Auto-log calls and AI summaries.

  4. 04

    Set up a power dialer campaign

    Import a list, configure dispositions, and start dialing.

  5. 05

    Train the AI Receptionist on your business

    Provide knowledge sources, escalation rules, and tone guidance.

  6. 06

    Send your first SMS via the REST API

    Authenticate, format the payload, and handle delivery webhooks.

SDKs & API

Build in your stack.

First-party SDKs and a stable REST API. HMAC-signed webhooks for every call, message, and AI event.

send-sms.ts@ringflow/node
import Ringflow from "@ringflow/node"

const rf = new Ringflow({ apiKey: process.env.RF_API_KEY })

const message = await rf.messages.send({
  from: "+14155550123",
  to:   "+14155550987",
  body: "Your appointment is confirmed for Thursday at 2:30 PM.",
})

console.log(message.id, message.status)
// "msg_01J9Z…", "queued"
Sent in < 200 msRead the SDK guide

Our Commitment

Documentation built for developers.

Every guide, reference page, and code sample is written by engineers who build and use the API. We treat docs as a product — versioned, tested, and updated with every release.

REST API reference
Webhook documentation
SDK quickstarts
Code examples
Postman collection
Sandbox environment
Changelog
Community forum

Built by teams who actually ship.

Engineers and platform teams shipping voice, SMS, and AI workflows on top of Ringflow — in days, not quarters.

P

Priya Anand

Staff Engineer, Loop Labs — Remote

We replaced two vendors with the Ringflow REST API in a single sprint. Webhook signatures are clean, the SDK retries are sensible, and the docs actually match the responses.

Verified Customer
M

Marcus Hill

VP Engineering, Forge Health — Boston, MA

The Node SDK shipped to production on day three. Our team came from another provider that took weeks to get past the auth flow — Ringflow's quickstart and code samples are the difference.

Verified Customer
S

Sofia Lin

Platform Architect, BrightWave SaaS — Austin, TX

AI Receptionist + webhook events let us automate ticket creation from inbound calls in under a day. The docs around HMAC signing and event retries saved us a real on-call incident.

Verified Customer
D

Daniel Okafor

Senior Developer, Atlas Logistics — Chicago, IL

Number porting docs walked our ops team through the LOA without a single support ticket. The tutorials read like they were written by people who actually ship code.

Verified Customer

FAQ

Developer questions, answered.

Proactively answering FAQs boosts user confidence and cuts down on support tickets.

Sign up for a Ringflow account, open Settings → API & Webhooks, and click Create API key. Keys are scoped per environment (sandbox vs. production) and can be rotated at any time without downtime.
Yes. Default limits are 60 requests/second per workspace for read endpoints and 30 requests/second for write endpoints. Limits are returned in the X-RateLimit-* response headers, and Enterprise plans can request higher quotas.
Every webhook includes an X-Ringflow-Signature header containing an HMAC-SHA256 of the raw body using your webhook secret. The Node and Python SDKs ship with a verifyWebhookSignature helper — see /docs/webhooks for code samples.
Yes. Every workspace ships with a sandbox that exposes the full API surface against simulated calls and messages. Sandbox numbers are free and isolated from billing — perfect for CI and integration tests.
Node.js (TypeScript-first) and Python are officially maintained. Community SDKs exist for Go, Ruby, and PHP — the REST API is the source of truth, and any HTTP client works.
Open an issue on the public Ringflow API GitHub repo, or reach our developer support team via the Community forum. Critical security issues should go to security@ringflow.com.

Ship voice, SMS, and AI in your product. Today.

Free sandbox · No card required · API live in 5 minutes