Skip to main content
All CollectionsTelnyx Identity & Verification Tools
Migrate Your LRN Lookup API from v1 to v1.1
Migrate Your LRN Lookup API from v1 to v1.1

A new version of the LRN lookup has been released. You can now return NPAC ten-digit numbers.

Shubam avatar
Written by Shubam
Updated over 11 months ago

We’ve released a new version of the LRN Lookup API (version 1.1), which is now able to return NPAC ten-digit numbers. 

A quick recap of the format of an LRN:

A picture of the LRN format.
  • N can be any number from 2 to 9

  • P, A, can be any number from 0 to 9

  • X can be any number from 0 to 9

What’s changed in v1.1:

  • The version in the URI path has changed from v1 to v1.1

  • The response in v1.1 is always a 10 digit number (NPA-NXX-XXXX), in v1 it was a 6 digit number (NPA-NXX)

  • If you are a customer of NPAC, the response will be the full 10 digits.

  • If you aren’t a customer of NPAC, the response will be the same first 6 digits as in v1 and then we’ll pad the final 4 digits with 9999.

Examples:

LRN lookup using the v1 API 

Request

Response

{"tn":"1234567890", "lrn":"301710"}

LRN lookup using the v1.1 API if you aren’t a customer of NPAC

In this case you just need to update the request API and check that you are able to handle the updated response for the LRN value.

Request

Response

{"tn":"1234567890", "lrn":"3017109999"}

LRN lookup using the v1.1 API if you are a customer of NPAC 

  1. Select“Telco Data” from the left-hand side navigation (see 1 below)

  2. Identify the LRN Lookup connection that you’re using from your list of Telco Data connections (see 2 below). 

  3. Select the settings icon on the right-hand side and from the dropdown click on “Edit Profile” (see 3 below). 

Telnyx Mission Control Portal.

5. Next, check the “Permitted NPAC User” checkbox

Permitted NPAC User tab.

6. Finally, update the request API and check that you’re able to handle the updated response for the LRN value.

Request

Response

{"tn":"1234567890", "lrn":"3017106199"}

That’s it. You’re all set to start using the new version of the API. 


Did this answer your question?