SDKs Overview
Firetell provides official client libraries and SDKs to simplify integration, handle WebRTC calling, and manage WebSocket communication within your applications.
Using our SDKs ensures that best practices—such as automatic reconnects, authentication timeouts, and media track management—are handled for you out of the box.
Server SDKs
Server-side SDKs authenticate with your Workspace Domain and API Secret Key (sk-...) to interact with the Firetell Workspace REST API from your backend services.
Node.js / TypeScript Server SDK
The @firetell/firetell-node-sdk library is the official server-to-server SDK for the Firetell Workspace API in Node.js (JavaScript & TypeScript, ESM & CommonJS). Authenticated with your workspace domain and API secret key, it supports programmable calls, SMS/MMS messaging, Voice AI agents, Knowledge Bases, recordings, transcriptions, SIP accounts, and webhook signature verification with zero runtime dependencies.
- Package:
@firetell/firetell-node-sdk - Repository:
github.com/firetellcom/firetell-node-sdk(MIT License) - Status: Active / Stable
- Guides: Installation & Setup • Quickstart Guide • API Reference • Changelog
Client SDKs (WebRTC)
Client-side SDKs authenticate with short-lived Agent JWT tokens for real-time WebRTC audio/video calling and presence events in web and mobile apps.
Web Browser SDK (JavaScript / TypeScript)
The @firetell/firetell-client-sdk library is compatible with browser environments (using ES Modules or loaded via a CDN script tag) for building WebRTC-based calling applications, and Node.js environments (using CommonJS) for receiving real-time events via WebSocket connection. It enables you to integrate real-time voice, video, and event features directly into your applications.
- Package:
@firetell/firetell-client-sdk - Status: Active / Stable
- Interactive Live Demo: https://firetell.com/docs/firetell-client-sdk/example/
- Guides: Installation & Setup • Client Authentication • Quickstart Guide • API Reference
Flutter SDK
The firetell_flutter_sdk package enables native iOS and Android apps to make and receive VoIP calls using WebRTC, with full support for push notifications (FCM & APNs), CallKit (iOS), and ConnectionService (Android).
- Package:
firetell_flutter_sdk - Status: Active / Stable
- Guides: Installation & Setup • Quickstart Guide • VoIP Push Notifications • API Reference
Looking for no-code / low-code workflow integrations (such as n8n)? See the Integrations Overview.
Handling Concurrent Incoming Calls
When multiple incoming calls arrive simultaneously or an incoming call arrives while an agent is currently on an active call, Firetell supports two standard frontend integration patterns:
Pattern A: Call Waiting & Hold (Multi-Call Management)
Allow the agent to receive call waiting notifications, put the current call on hold, and answer the new incoming call:
- JavaScript / TypeScript
- Flutter / Dart
let activeCall: Call | null = null;
client.events.on("call.offer", async (incomingCall: Call) => {
if (activeCall && activeCall.active) {
// 1. Show Call Waiting notification on UI
console.log(
`Call Waiting from ${incomingCall.from} (${incomingCall.from_name})`,
);
// 2. When Agent clicks "Hold & Answer":
await activeCall.hold();
await incomingCall.accept();
activeCall = incomingCall;
} else {
// Single call flow
activeCall = incomingCall;
}
});
Call? activeCall;
client.onCallOffer.listen((incomingCall) async {
if (activeCall != null && activeCall!.active) {
// 1. Show Call Waiting notification on UI
print('Call Waiting from ${incomingCall.from} (${incomingCall.fromName})');
// 2. When Agent taps "Hold & Answer":
await activeCall!.onhold();
await incomingCall.accept();
activeCall = incomingCall;
} else {
activeCall = incomingCall;
}
});
Pattern B: Auto-Reject / Busy (Single-Call Policy)
If your call center policy restricts agents to one call at a time:
- JavaScript / TypeScript
- Flutter / Dart
client.events.on("call.offer", async (incomingCall: Call) => {
if (client.activeCalls.size > 1) {
// Auto-reject 2nd call with Busy status (SIP 486 Busy)
// The backend Call Flow will immediately execute the fallback branch (Voicemail/Reroute)
await incomingCall.reject();
}
});
client.onCallOffer.listen((incomingCall) async {
if (client.activeCalls.length > 1) {
// Auto-reject 2nd call with Busy status (SIP 486 Busy)
// The backend Call Flow will immediately execute the fallback branch
await incomingCall.reject();
}
});
Planned SDKs
We are actively developing SDKs for additional languages and mobile frameworks to help you build native apps:
| Platform / Language | Status | Package Name | Target Environment |
|---|---|---|---|
| React Native | 🔜 Planned | firetell-react-native-sdk | iOS & Android |
If you need an SDK for another language, please reach out to us at [email protected].