Skip to main content
The https://api.telnyx.com/v2 conventions apply to the current Telnyx REST API. Telnyx also provides active product-specific interfaces with different protocols, authentication, media types, and response contracts. These interfaces are not deprecated merely because they do not use the V2 REST conventions.

​
Active product-specific interfaces

  • Cloud Storage S3 operations use S3-compatible credentials and AWS Signature Version 4. Follow Cloud Storage API endpoints.
  • WebRTC clients use short-lived client tokens and WebRTC signaling rather than a server-side Telnyx API key.
  • WebSocket APIs define connection-specific authentication messages, event schemas, and lifecycle behavior. Follow the selected product’s WebSocket guide.
  • Webhook deliveries are inbound callbacks with product-specific validation and acknowledgment contracts. Follow Webhook fundamentals and the selected product’s webhook reference.
Do not apply V2 REST authentication, JSON envelopes, methods, pagination, or retry behavior to these interfaces unless their own documentation declares the same contract.

​
Retired HTTP API inventory

Do not use these HTTP endpoints for new integrationsThe endpoints below predate the current V2 REST API. Use the current API reference for new integrations. Contact Telnyx Support before changing an existing integration that still depends on one of them.
  • https://api.telnyx.com/origination
  • https://api.telnyx.com/termination
  • https://api.telnyx.com/messaging
  • https://api.telnyx.com/reporting
  • https://api.telnyx.com/security
  • https://api.telnyx.com/account
  • https://api.telnyx.com/caller-information
  • https://api.telnyx.com/LRN
  • https://api.telnyx.com/LRNLookup
  • https://sms.telnyx.com/messages

​
Existing DNS ENUM and XML UDP integrations

DNS ENUM and XML UDP behavior is outside the V2 REST contract. Do not infer its lifecycle or migration path from the REST API version. Contact Telnyx Support before creating or modifying an integration that depends on api.telnyx.com or lrnlookup.telnyx.com through those protocols.

​
Migration

No universal one-to-one migration applies to retired or protocol-specific interfaces. Locate the corresponding current product in the API reference, compare schemas and operational behavior, and validate the replacement in a non-production environment. Use API versions and deprecations for the migration checklist.