# /LRN is deprecated

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

Telnyx deprecated the legacy /LRN* endpoints without a shutdown date. Calls to these paths will eventually fail, as they predate the current V2 REST API and are retired from use in new integrations.

## What to use instead

Look up a number's carrier and routing with GET /v2/number_lookup/{phone_number}?type=carrier instead. Moving takes more than changing an identifier, as there is no direct one-to-one replacement and 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.

- API: Telnyx API (api.telnyx.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/LRN*`
- 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/lrn-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
