# /messaging is deprecated

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

Telnyx has deprecated calls matching /messaging* without a shutdown date. These endpoints predate the current V2 REST API, and requests to them will fail. The change applies across the platform for integrations relying on the retired HTTP API inventory.

## What to use instead

Send messages using POST api.telnyx.com/v2/messages and manage numbers through /v2/messaging_phone_numbers instead. Migrating takes more than changing an identifier, as there is no direct replacement and developers must choose and validate the matching V2 product.

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

- API: Telnyx API (api.telnyx.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/messaging*`
- Source: [Announcement](https://developers.telnyx.com/docs/development/api-fundamentals/legacy-apis)
- Verified: November 6, 2026, against Telnyx API's own pages
- Page: https://www.okapi.bot/providers/telnyx-api/breaking-changes/messaging-is-deprecated/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent