Choose an SDK
TypeScript and Node.js
npm package, setup, API usage, pagination, and error handling.
Python
Sync and async clients, typed models, pagination, and error handling.
Go
Go modules, request options, pagination, and error handling.
Java
Gradle and Maven setup, sync and async clients, and typed models.
Ruby
Bundler setup, typed models, pagination, and error handling.
PHP
Composer setup, named parameters, pagination, and error handling.
SDK or direct HTTP
Select the interface that matches the workload:
Every REST endpoint remains available over HTTPS. The API reference provides endpoint schemas and request examples when direct HTTP is the better fit.
Install
Authenticate
Create an API key in the Mission Control Portal, store it outside source control, and expose it to the application asTELNYX_API_KEY. Pass this environment variable when initializing the client; SDKs that support environment-based defaults read the same name.
Make a request
The following TypeScript example initializes the client fromTELNYX_API_KEY and creates a call:
Generated API coverage
Telnyx generates the server-side SDKs from the public REST API definition. Resource and method names follow the API model, while each library provides language-specific types and conventions. All official server-side SDKs include utilities for ED25519 webhook-signature verification. Use the SDK’s webhook service with the raw request body, thetelnyx-signature-ed25519 header, the telnyx-timestamp header, and the public key from the Mission Control Portal.
SDK releases can follow API changes at different times. Before adopting a newly released endpoint or field:
- Update to the current SDK release.
- Check the language guide or repository for the generated method and model.
- Use direct HTTP when an API capability is available before the matching SDK release.