Skip to content
Developers

Build on the work RapidRoot already handles.

Messaging, Voice, Hostels and Real Estate already run the operational workflow — shared inbox, campaigns, calls, stays and bookings. Build around it via the platform foundation where APIs exist today, without rebuilding tenancy or billing yourself.

Public APIs are in active development

Every endpoint on this page is labelled as available, in development, or coming soon. Nothing describes an endpoint you cannot use yet. Pilot customers get early access and direct engineering support.

Platform foundation — what is actually there

RapidRoot Core owns identity, organizations, products, billing, entitlements and admin. Communication and Operations run as separate workspaces on top — no falsely unified customer graph. Your systems → RapidRoot → operational workflow.

Identity & Organizations

Accounts, workspaces, membership and tenancy — the boundary every request is checked against.

Products & Entitlements

Lifecycle and feature gating — which workspace can use Messaging, Voice, Hostels, Real Estate.

Billing

Plans, usage and invoices — product-scoped, verified implementation, no invented economics.

Admin & Roles

Server-enforced roles and member management — not just hiding buttons.

Contacts & Timeline

Where available, a shared customer timeline across messaging and voice — not claimed as universal.

APIs & Webhooks

Where shipped, product APIs and outbound events mirroring the operational flow.

Messaging = Available, Voice = Pilot — guided access, Hostels/Real Estate = Live standalone workspaces, Automation = In development, AI Agents = Coming soon. APIs mirror product maturity.

Platform architecture

How RapidRoot sits between your business systems and your customers.

Business applications

CRM, helpdesk, ERP, internal tools and websites.

REST APIs

Messaging, voice, contacts. In development.

Platform core

Messaging Cloud, Voice Cloud, shared analytics.

Webhooks

Outbound events to your endpoints. In development.

Integrations

Channel providers and business systems.

Messaging CloudVoice CloudContactsAnalytics

Developer resources

Available

Documentation

Concepts, integration guides and platform behaviour.

In development

API reference

Planned resource model, request and response format.

In development

Authentication

API keys, bearer tokens, rotation and secret handling.

In development

Webhooks

Event-driven delivery, retries and signature verification.

Coming soon

SDKs

Client libraries, current status and language roadmap.

Coming soon

API Explorer

Browse endpoints and test requests from the browser.

Available

Integrations

What connects today and what is on the roadmap.

Available

Changelog

Platform releases, improvements, fixes and known issues.

In development

Status

Service availability and maintenance communication.

Available

Support

How to reach the engineering team with technical questions.

In development

API overview

JSON over HTTPS. API key bearer auth. Consistent error codes. Versioned endpoints with published deprecation.

  • REST over HTTPS
  • API key authentication
  • JSON request and response bodies
  • Consistent HTTP status codes
  • Versioned endpoints
Example request format
POST /v1/messages
Authorization: Bearer <API_KEY>

{
  "channel": "whatsapp",
  "to": "+9198XXXXXXXX",
  "template": "order_shipped",
  "variables": {
    "order_id": "RR-4821"
  }
}

Illustrative. Endpoints not yet publicly available.

Developer roadmap

Available today

  • Platform and architecture documentation
  • Messaging and voice product documentation
  • Integration catalogue with honest status labels
  • Direct technical support during pilots

In development

  • REST API for messaging and voice
  • API key authentication and rotation
  • Signed webhook delivery
  • Node.js SDK

Planned

  • Interactive API Explorer
  • Postman collection
  • Python, Java and Go SDKs
  • Full-text documentation search
  • Live status monitoring