Telnyx API /origination* endpoint removal

Deprecated, no dateSubscribe to Telnyx APIShare

Telnyx deprecated the /origination* endpoints without a shutdown date. These legacy endpoints predate the V2 REST API, and requests sent to them fail. Developers should not use these endpoints for new integrations.

Calls it hits

/origination*

What to use instead of these calls

Manage inbound routing using the V2 resources, such as connections and phone numbers, under api.telnyx.com/v2. Because there is no direct one-to-one replacement, the matching V2 product must be chosen and validated.

Telnyx names no one-to-one replacement for its retired HTTP APIs: the matching V2 product must be chosen and validated.

In Telnyx API's words

Retired HTTP API inventory Do not use these HTTP endpoints for new integrations The endpoints below predate the current V2 REST API.

Telnyx API, Announcement

Facts

API: Telnyx API api.telnyx.com
Kind: Endpoint removal
Takes effect: No date given yet
Calls after that day: Fail
Source: Announcement
Last updated: October 26, 2026
Verified: November 6, 2026, against Telnyx API's own pages

Questions

When does this change take effect?

Telnyx API deprecated /origination* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Telnyx API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub