Trestle’s Reverse Phone API performs international reverse phone lookups across 100+ countries, returning phone validity, line type, carrier, name, and address matching where available. Built for fraud prevention, it’s GDPR-compliant and priced the same worldwide under a single API, single contract, and single global price. International coverage is available to enterprise customers on a per-customer basis, with an average response time of roughly 500 milliseconds.
What is our global reverse phone lookup coverage? #
| U.S. | International (Non-U.S.) | ||
| Attribute Category | Coverage | Accuracy | Coverage |
| Phone Validity | 100% | 100% | 100% |
| Line Type | 99+% | 99+% | 99+% |
| Phone Carrier | 99+% | 99+% | 99+% |
| Phone to Name Match | 93% | 90+% | BR (Brazil): 85%CA (Canada): 70%UK: 50%Rest of World: 30–50% |
| Subscriber Address | 90% | 90+% | Brazil: 80% |
How can you enable global coverage for Reverse Phone API? #
Currently international coverage for Reverse Phone API is available for enterprise users.
Enterprise users can contact us at support@trestleiq.com and share their use case, and our sales representatives will be able to enable this feature.
Please note: Unlike Phone Validation API, which provides global coverage by default, Reverse Phone API (Version 3.2) only supports international coverage on a per-customer basis.
How many countries does our international reverse phone lookup cover? #
International reverse phone lookup coverage is available across 100+ countries, and it varies by country. See the country-by-country phone-to-name coverage table below, or our article Which Countries’ Data Do You Have? for more information.
What is the response time/latency of the API with international coverage enabled? #
The average response time is 500 milliseconds. We expect the P95 latencies to be around one second.
Does the international Reverse Phone API comply with data privacy regulations globally? #
Yes. Trestle operates as a fully GDPR-compliant processor and collaborates exclusively with data vendors who also comply with relevant data protection regulations.
Does using Reverse Phone API with international numbers cost more? #
No, the pricing remains the same. This aligns with our core principle of offering a single API, single contract, and single global price – regardless of location. For more details, check out our pricing page.
What is the accuracy of the returned data? #
We feel confident about the data available sourced from authoritative sources. As we continue to test with our customers, we will publish more specific data on a country-by-country basis.
Why only Reverse Phone API? Would we add international support for other APIs as well? #
We are enabling international coverage specifically for Reverse Phone API because its use case (fraud prevention) aligns with global privacy regulations, including GDPR and our contractual obligations. Under Article 47 of the GDPR, the use of identity data for fraud prevention is permitted without requiring user consent. As a result, no other use case will be allowed outside the U.S.
A deep-dive into our non-U.S. phone-to-name coverage #
Phone-to-name coverage for international reverse phone lookups is grouped into three levels:
- Low: Phone-to-name coverage below 30%
- Medium: Phone-to-name coverage between 30-70%
- High: Phone-to-name coverage above 70%
| Country | Phone-to-Name Coverage Level |
| Afghanistan | Low |
| Albania | Medium |
| Algeria | Low |
| Andorra | Medium |
| Angola | Medium |
| Argentina | Low |
| Armenia | Low |
| Australia | Medium |
| Austria | Medium |
| Azerbaijan | Low |
| Bahrain | Medium |
| Bangladesh | Low |
| Belarus | Low |
| Belgium | High |
| Belize | Medium |
| Bhutan | Low |
| Bolivia | Medium |
| Bosnia and Herzegovina | Low |
| Botswana | Low |
| Brazil | High |
| Bulgaria | Medium |
| Burkina Faso | Low |
| Burundi | Low |
| Cambodia | Low |
| Cameroon | Low |
| Canada | High |
| Cape Verde | Medium |
| Chad | Low |
| Chile | Medium |
| China | Low |
| Colombia | Medium |
| Congo | Low |
| Costa Rica | Medium |
| Croatia | Medium |
| Cuba | Low |
| Cyprus | High |
| Czech Republic | Medium |
| Denmark | Medium |
| Djibouti | Low |
| Ecuador | Medium |
| Egypt | Medium |
| El Salvador | Low |
| Equatorial Guinea | Low |
| Eritrea | Low |
| Estonia | Medium |
| Ethiopia | Low |
| Faroe Islands | Low |
| Fiji | Low |
| Finland | Medium |
| France | Medium |
| French Polynesia | Medium |
| Gabon | Medium |
| Georgia | Medium |
| Germany | Medium |
| Ghana | Low |
| Gibraltar | Medium |
| Greece | Medium |
| Guatemala | Low |
| Guinea | Low |
| Guyana | Medium |
| Haiti | Low |
| Honduras | Medium |
| Hong Kong | Low |
| Hungary | Medium |
| Iceland | Medium |
| India | Medium |
| Indonesia | Low |
| Iran | Medium |
| Iraq | Medium |
| Ireland | Medium |
| Israel | Medium |
| Italy | High |
| Japan | Medium |
| Jordan | Low |
| Kenya | Low |
| Kiribati | Low |
| Kuwait | Medium |
| Kyrgyzstan | Low |
| Latvia | Medium |
| Lebanon | Medium |
| Lesotho | Low |
| Liberia | Low |
| Libya | Medium |
| Liechtenstein | Medium |
| Lithuania | Medium |
| Luxembourg | Medium |
| Madagascar | Low |
| Malawi | Low |
| Malaysia | Medium |
| Maldives | Medium |
| Mali | Low |
| Malta | High |
| Mauritania | Low |
| Mauritius | Low |
| Mexico | Medium |
| Micronesia | Low |
| Moldova | Low |
| Monaco | Low |
| Mongolia | Low |
| Montenegro | Low |
| Morocco | Medium |
| Namibia | Medium |
| Nepal | Low |
| Netherlands | Medium |
| New Zealand | Medium |
| Nicaragua | Low |
| Niger | Low |
| Nigeria | Low |
| North Korea | Low |
| Norway | High |
| Oman | Medium |
| Pakistan | Low |
| Palestine | Medium |
| Panama | Low |
| Papua New Guinea | Low |
| Paraguay | Medium |
| Peru | Medium |
| Philippines | Low |
| Poland | Medium |
| Portugal | High |
| Qatar | Medium |
| Romania | Medium |
| Russia | Low |
| Rwanda | Low |
| San Marino | Low |
| Saudi Arabia | Medium |
| Senegal | Low |
| Serbia | Medium |
| Seychelles | Medium |
| Sierra Leone | Low |
| Singapore | Medium |
| Slovakia | Medium |
| Slovenia | Medium |
| Solomon Islands | Low |
| South Africa | Low |
| South Korea | Low |
| Spain | Medium |
| Sri Lanka | Low |
| Sudan | Low |
| Suriname | Low |
| Swaziland | Low |
| Sweden | Medium |
| Switzerland | Medium |
| Syria | Medium |
| Taiwan | Medium |
| Tajikistan | Low |
| Tanzania | Low |
| Thailand | Medium |
| Tonga | Low |
| Tunisia | Medium |
| Turkey | Medium |
| Turkmenistan | Low |
| Uganda | Low |
| Ukraine | Low |
| United Arab Emirates | Medium |
| United Kingdom | Medium |
| Uruguay | Low |
| Uzbekistan | Low |
| Vanuatu | Low |
| Venezuela | Medium |
| Vietnam | Low |
| Yemen | Low |
Frequently Asked Questions #
Which countries does the international reverse phone lookup support?
International Reverse Phone API supports phone numbers across 100+ countries. Phone validity, line type, and carrier are returned for international numbers, while phone-to-name and subscriber address coverage varies by country (see the coverage table above).
Is there a free international reverse phone lookup?
International coverage is an enterprise feature that is enabled on a per-customer basis, so it isn’t part of the self-serve free trial. You can still start a free Reverse Phone API trial to test U.S. coverage, then contact us to enable international numbers for your use case.
How do I look up an international phone number with Trestle?
Once international coverage is enabled for your enterprise account, you query the Reverse Phone API the same way you would for a U.S. number. You pass the phone number to the endpoint and receive validity, line type, carrier, and (where available) name and address data in the response. See our Reverse Phone API documentation for request and response specifics.
Ready to run international reverse phone lookups? Contact our team at support@trestleiq.com to enable international coverage for your enterprise account, or explore Reverse Phone API to learn more.