/v1 API.
Use the API directly if you want raw HTTP. Use an SDK when you want faster setup, typed responses, and a language-native workflow.
Choose your interface
| Interface | Status | Good for |
|---|---|---|
| Python SDK | Available now | Automation, scripts, backends, local testing |
| TypeScript SDK | Available now | Node.js apps, serverless functions, full-stack TypeScript |
| CLI | Available now | Local workflows, one-off calls, debugging, CI pipelines |
| HTTP / cURL | Available now | Raw API access, testing, custom integrations |
How the pieces fit together
What the SDKs handle for you
- Authentication with your API key
- JSON request building for calls and numbers
- Typed response objects instead of raw dictionaries
- Cleaner workflows for polling and number management
- Language-native naming (for example Python uses
from_instead offrom)
Start here
Python SDK
Install the Python package, point it at production or local dev, buy numbers, and place calls.
TypeScript SDK
Install the npm package, use typed async methods for numbers and calls.
CLI
Install with
pip install 'callingbox[cli]' and place calls straight from your terminal.API quickstart
Make your first call with cURL, Python, or TypeScript examples.
API basics
Base URL, authentication, endpoint conventions, and the public
/v1 model.API Reference
Interactive request builders powered by the OpenAPI spec.