Skip to content
DevelopersComing soon

SDKs

Client libraries for the RapidRoot platform. Only the Node.js library is being actively built today; every other language is listed as planned.

Libraries

Node.js SDK

In development

JavaScript / TypeScript

First client library being built alongside the API. Available to pilot customers first.

Python SDK

Coming soon

Python

Planned after the Node.js library stabilises.

Java SDK

Coming soon

Java

Planned for enterprise integration teams.

Go SDK

Coming soon

Go

Planned. Timeline not committed.

REST + HTTP

In development

Any language

Plain HTTP will always be a supported path — an SDK is never required.

Example usage

The Node.js library is not published to a package registry yet, so the snippet below shows the intended shape rather than an installable package.

Example format — package not published yet
import { RapidRoot } from "@rapidroot/node";

const rr = new RapidRoot({ apiKey: process.env.RAPIDROOT_API_KEY });

await rr.messages.send({
  channel: "whatsapp",
  to: "+9198XXXXXXXX",
  template: "order_shipped",
  variables: { order_id: "RR-4821" },
});
Example format — plain HTTP, no SDK required
curl -X POST https://api.rapidroot.example/v1/messages \
  -H "Authorization: Bearer $RAPIDROOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"channel":"whatsapp","to":"+9198XXXXXXXX","template":"order_shipped"}'

Postman collection

Coming soonPostman collection planned.

A downloadable collection will be published alongside the public API so teams can evaluate endpoints without writing code first.

Design principles

  • Thin wrappers over the REST API — no hidden behaviour you cannot reproduce with curl.
  • Typed request and response models where the language supports it.
  • Built-in retry with backoff for transient failures, disabled by default for non-idempotent calls.
  • Server-side use only; SDKs will never be designed for browser bundles.