Reverse Phone API
Reverse Phone API
Reverse Phone API offers comprehensive verification and enrichment of phone numbers. It includes phone validity, line type, carrier data, and all owners associated with the phone and their details, like demographics and current addresses.
Reverse Phone API 3.2
Query Parameters
The phone number in E.164 or local format. The default country calling code is +1 (USA). Example:
phone=2069735100The ISO-3166 alpha-2 country code of the phone number. See: ISO-3166. Example:
phone.country_hint=USPerson or Business name associated with the phone number. If multiple names are associated with the phone in Trestle’s database, this name will be ranked higher. Example:
phone.name_hint=John DoeThe postal code of the subscriber address associated with the phone number. If multiple names or addresses are associated with the phone in Trestle’s database, this postal code hint will be used to rank name/address higher. Example:
phone.postal_code_hint=98264Header Parameters
Your API key for authentication. Example:
{{ apiKey }}Response
The persistent ID of the phone number. Format:
Phone.<uuid>The phone number in E.164 or local format. The default country calling code is +1 (USA).
True if the phone number is valid.
The country code of the phone number.
The line type of the phone number. Possible values:
Landline- Traditional wired phone lineMobile- Wireless phone lineFixedVOIP- VOIP number connected to a physical addressNonFixedVOIP- VOIP number unconnected to a fixed physical addressPremium- Caller pays a premium for the callTollFree- Callee pays for callVoicemail- Voicemail-only serviceOther- Line type is unclear
The company that provides voice and/or data services for the phone number. Carriers are returned at the MVNO level.
True if the phone is associated with a prepaid account.
True if the phone number is registered to a business.
The owner(s) associated to the phone.
Error details in case of an error.
Warnings returned as part of the response, if applicable.Enum: Invalid Input International number. Not authorized Missing Input
Error Responses
400 Bad Request
The server cannot process the request due to client-side errors.Check for: Syntax errors in the request script, malformed JSON, or invalid parameters.403 Forbidden
The request is understood, but the server is refusing to fulfill it.- Invalid API Key: The key is incorrect or deactivated. Check for: Trailing spaces, syntax errors, or incorrect character counts.
- API Key Missing: The request header did not include an API key.
- API Key Disabled (Portal Issue): The key is inactive. Check for: Insufficient funds in your self-serve wallet or if a Trestle Admin manually deactivated your API key.
- API Key does not have Product Access (Portal Issue): The API key is active, but it is not enabled for this product or API version. Check for: Incorrect endpoint, incorrect API version, or missing product access on the key.
- API Key Expired: The key has reached its end-of-life (primarily affects Trial users).
429 Too Many Requests
You have sent too many requests in a given amount of time.- Rate Limit Exceeded: You have surpassed the queries-per-second (QPS) threshold for your tier.
- Quota Exceeded (Portal Issue): You have reached the total volume allowed for your current billing cycle. Upgrade your plan in the portal to resume service.
