Endpoints
US Zip Code Radius & Lookup API 5
What is the US Zip Code Radius and Lookup API?
U.S. ZIP code lookup, radius search, and distance API for fast and accurate geolocation. Instantly retrieve ZIP code details, find nearby ZIPs within a radius, calculate distances between ZIP codes, autocomplete ZIP inputs, and map cities to ZIPs. Designed for delivery zones, store locators, logistics platforms, and location-based services.
US Zip Code Radius and Lookup API is available on the JoJ API marketplace. Subscribe with a single JoJ API key, call it through one gateway, and pay from one wallet — no separate account or contract with the provider.
US Zip Code Radius and Lookup API endpoints
- GET
/zipcode/v1/distanceDistance Between Two Zip Codes
Computes the geographical distance between two specified US zip codes, returning the value in either miles or kilometers.
- GET
/zipcode/v1/radiusZip Codes In Radius
Retrieves a list of US zip codes that fall within a specified radius (in miles or kilometers) of a given origin US zip code.
- GET
/zipcode/v1/by-cityZip Codes By State & City
Retrieves a list of all US zip codes associated with a given city name and a two-letter state abbreviation.
- GET
/zipcode/v1/autocompleteAutocomplete Suggestions (City and Zip Code)
Provides a list of US zip code suggestions based on a partial query string. Useful for implementing type-ahead features.
- GET
/zipcode/v1/lookup/{zip}US Zip Code Info
Retrieves city and state information associated with a given US zip code.
Frequently asked questions about US Zip Code Radius and Lookup API
Where does the ZIP code data come from, and how often is it updated?
The data comes from official USPS Postal Bulletins. The database holds 43,623 active ZIP codes with city, state and coordinates. Each new bulletin is processed within 7 days of publication, which covers new ZIP codes, boundary realignments, city name changes and post office closures.
What does a response with "found": false mean?
A miss is not an error. The request was valid and no record matched, so the response is HTTP 200 with "success": true and "found": false. Reserve error handling for 4xx and 5xx codes, and treat "found" as the data question. All timings are reported in the X-Response-Time and Server-Timing headers.