API/MCP Access
Current API/MCP serviceTelcoData's current API and MCP service lives at https://api.telcodata.us.
Your API key
Do not share this key. It identifies your account and is required for authenticated API/MCP requests. You can regenerate it from your account profile if needed.
Access requirements
API access requires an active account with Advanced Class or better. Queries will reject if the account is allowed to lapse.
Bulk downloads
For full data files, you can use FTP at ftp.telcodata.us with the same username and password you use for the website. FTP downloadable files require Advanced Class access or better.
The current API at https://api.telcodata.us also supports downloadable-file access for automation. Use your API key above with the download/file listing and retrieval calls documented on the API/MCP service. This is the preferred option for scripts that already use API-key authentication.
If you are sending very large volumes of requests, please consider using the downloadable data files locally. That is usually faster and lighter for million-query workflows.
Legacy query documentation
The older query endpoints below remain documented for legacy integrations. New work should start with https://api.telcodata.us and the MCP/API documentation there.
Legacy interfaces documented here:
queryexchangevalid - This is a simple flat text file giving "title=data" type formats. This is intended mostly for verifying an exchange is valid.
queryexchangexml - This is a similar interface, designed for retrieving data on a single exchange. Returns data in XML format.
queryareacodexml - This is a mass transfer interface, the information this gives is in bulk quantities. It's preferred you cache it, but low volume pulls are probably okay. Data is returned in XML format.
queryexchangevalid
URL: /query/queryexchangevalid.htmlParameters:
npa [required] - 3 digit "area code"
nxx [required] - 3 digit exchange
apikey [required] - The API key from your accountExample: http://www.telcodata.us/query/queryexchangevalid.html?npa=248&nxx=455&apikey=
Notes: Order of text may change. Treat as "variable=value" pairs. Don't be dependent on the order of the text in the returned data.
queryexchangexml
URL: /query/queryexchangexml.htmlParameters:
npa [required] - 3 digit "area code"
nxx [required] - 3 digit exchange
apikey [required] - The API key from your accountExample: http://www.telcodata.us/query/queryexchangexml.html?npa=248&nxx=455&apikey=
Notes: Additional values may be returned in the future.
queryareacodexml
URL: /query/queryareacodexml.htmlParameters:
npa [required] - 3 digit "area code"
apikey [required] - The API key from your account
Example: http://www.telcodata.us/query/queryareacodexml.html?npa=947&apikey=
Notes: Additional values may be returned in the future.