The US ZIP Code Distance Fetcher API is a tool designed to quickly and accurately calculate the distance between two locations within the United States using their ZIP codes. Its operation is simple, efficient, and reliable, making it an ideal solution for logistics, e-commerce, route planning, geographic analysis, and transportation services applications.
This API stands out for its geographic accuracy, based on official coordinates from the US postal system. It provides real-time results, which is crucial for companies that need to optimize routes, calculate delivery times, or estimate transportation costs.
Its main benefits include response speed, ease of use, and compatibility with different programming languages. Users can use it to enrich applications with distance calculation, customer location, market segmentation by geographic area, or service coverage analysis features.
In summary, the US ZIP Code Distance Fetcher API provides a reliable and efficient method for determining the distance between two points in the United States, combining accuracy, ease of integration, and versatility. It is an essential tool for any project that requires accurate geographic data, distance calculations, or spatial analysis based on zip codes.
{
"success": true,
"message": "Distance Between two Zip Data feed successfully",
"data": {
"zip1": "90210",
"city1": "Beverly Hills",
"zip2": "10001",
"city2": "New York City",
"distance_km": 3948.24,
"distance_miles": 2453.32
}
}
curl --location --request GET 'https://zylalabs.com/api/11069/us+zip+code+distance+fetcher+api/20843/get+distance&zip_code2=Required' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Get Distance endpoint returns data that includes the distance between two U.S. ZIP codes, along with the corresponding cities for each ZIP code. The results are provided in both kilometers and miles.
The key fields in the response data include "zip1" and "zip2" (the input ZIP codes), "city1" and "city2" (the corresponding cities), "distance_km" (distance in kilometers), and "distance_miles" (distance in miles).
The response data is organized in a JSON format, with a "success" boolean indicating the request status, a "message" for additional context, and a "data" object containing the distance details and city information.
The Get Distance endpoint provides information on the distance between two ZIP codes, including the names of the cities associated with those ZIP codes and the calculated distance in both kilometers and miles.
The Get Distance endpoint accepts two parameters: "zip1" and "zip2," which should be valid U.S. ZIP codes. Users must ensure that both parameters are provided for the calculation to be performed.
Data accuracy is maintained by using official coordinates from the U.S. postal system. Regular updates and quality checks ensure that the distance calculations reflect the most current geographic data.
Typical use cases include logistics and delivery route optimization, e-commerce applications for shipping cost estimation, geographic analysis for market segmentation, and transportation services planning.
Users can utilize the returned data to calculate delivery times, optimize routes based on distance, analyze service coverage areas, and enhance applications with geographic insights based on ZIP code distances.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
36ms
Service Level:
100%
Response Time:
349ms
Service Level:
100%
Response Time:
19ms
Service Level:
100%
Response Time:
236ms
Service Level:
100%
Response Time:
877ms
Service Level:
100%
Response Time:
90ms
Service Level:
100%
Response Time:
3,360ms
Service Level:
100%
Response Time:
50ms
Service Level:
100%
Response Time:
202ms
Service Level:
100%
Response Time:
165ms
Service Level:
100%
Response Time:
4,649ms
Service Level:
100%
Response Time:
5,101ms
Service Level:
100%
Response Time:
5,283ms
Service Level:
100%
Response Time:
4,909ms
Service Level:
100%
Response Time:
5,318ms
Service Level:
100%
Response Time:
56ms
Service Level:
100%
Response Time:
193ms
Service Level:
100%
Response Time:
219ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
59ms