SDKs

There's no published client library yet. Until then, call the public API directly with a personal API key — it's a standard Bearer-token + JSON REST API, so any HTTP client works.

Current status

Language	Status
Node.js / TypeScript	Planned
Python	Planned

Why there's no SDK yet

A generated or hand-written SDK is only as good as the API surface underneath it. The public partner API (/api/public/v1/) already has stable authentication (personal API keys and OAuth2) and versioning (v1), which is what an SDK would wrap, but the surface itself is intentionally narrow today (campaigns, agents, phone numbers, contacts, webhooks). An SDK will follow once that surface covers enough of the platform (agent management, knowledge base, calls) to be worth generating a client for, rather than shipping a thin wrapper around four endpoints.

In the meantime

• API Reference: every endpoint, request/response shape, and error case.
• Authentication: personal API keys (the simplest option for your own scripts) and the OAuth2 flow for third-party apps.
• Outbound Campaigns has copy-pasteable curl examples for the most common flow (create a campaign, queue contacts).

Want to be notified?

Reach out to iCallAgent to be added to the SDK beta list once one starts development.