The Reverse Geocode Data API allows you to obtain accurate and structured geographic information from latitude and longitude coordinates. When it receives a location, the API returns multiple levels of address data that allow you to accurately identify both specific points (such as an exact address) and broader areas (such as neighborhoods, cities, or counties).
The response includes a formatted_address field that represents the complete address in human-readable format. Address_components are also provided, detailing each element that makes up the address, including street number (street_number), street name (route), neighborhood (neighborhood), sublocality (sublocality), city (locality), county (administrative_area_level_2), state (administrative_area_level_1), country, and postal code. Each component comes with its long and short name, along with its corresponding type, which is useful for classification and visualization.
In addition, the API returns precise coordinates in the geometry.location field, including latitude and longitude values, along with the location_type indicating the level of accuracy (e.g., “ROOFTOP,” “APPROXIMATE,” or “GEOMETRIC_CENTER”). A viewport (display area) is also provided to facilitate geographic representation on maps.
In some cases, the response may include several hierarchical or alternative results, allowing access to nearby locations, associated buildings, intersections, or related points of interest. Plus codes (plus_code) with compound_code and global_code variants are also included, which are useful for representing locations without a formal address.
This API is ideal for geolocation applications, logistics, delivery services, territory analysis, address validation, map visualization, and geographic information systems (GIS). It supports multiple formats and levels of granularity, adapting to both precise needs and broader territorial analysis.
In short, the API delivers complete, structured, and reliable data to convert coordinates into geographic information that is understandable and usable by modern systems.
To use this endpoint, you must specify a latitude and longitude in the parameter.
Reverse geocoding - Características del Endpoint
| Objeto | Descripción |
|---|---|
latlng |
[Requerido] Enter coordinates |
{
"plus_code" :
{
"compound_code" : "P27Q+MCM New York, NY, USA",
"global_code" : "87G8P27Q+MCM"
},
"results" :
[
{
"address_components" :
[
{
"long_name" : "277",
"short_name" : "277",
"types" :
[
"street_number"
]
},
{
"long_name" : "Bedford Avenue",
"short_name" : "Bedford Ave",
"types" :
[
"route"
]
},
{
"long_name" : "Williamsburg",
"short_name" : "Williamsburg",
"types" :
[
"neighborhood",
"political"
]
},
{
"long_name" : "Brooklyn",
"short_name" : "Brooklyn",
"types" :
[
"political",
"sublocality",
"sublocality_level_1"
]
},
{
"long_name" : "Kings County",
"short_name" : "Kings County",
"types" :
[
"administrative_area_level_2",
"political"
]
},
{
"long_name" : "New York",
"short_name" : "NY",
"types" :
[
"administrative_area_level_1",
"political"
]
},
{
"long_name" : "United States",
"short_name" : "US",
"types" :
[
"country",
"political"
]
},
{
"long_name" : "11211",
"short_name" : "11211",
"types" :
[
"postal_code"
]
}
],
"formatted_address" : "277 Bedford Ave, Brooklyn, NY 11211, USA",
"geometry" :
{
"location" :
{
"lat" : 40.7142205,
"lng" : -73.9612903
},
"location_type" : "ROOFTOP",
"viewport" :
{
"northeast" :
{
"lat" : 40.71556948029149,
"lng" : -73.95994131970849
},
"southwest" :
{
"lat" : 40.7128715197085,
"lng" : -73.9626392802915
}
}
},
"navigation_points" :
[
{
"location" :
{
"latitude" : 40.7142498,
"longitude" : -73.9613696
}
}
],
"place_id" : "ChIJd8BlQ2BZwokRAFUEcm_qrcA",
"plus_code" :
{
"compound_code" : "P27Q+MF Brooklyn, NY, USA",
"global_code" : "87G8P27Q+MF"
},
"types" :
[
"street_address"
]
},
{
"address_components" :
[
{
"long_name" : "281",
"short_name" : "281",
"types" :
[
"street_number"
]
},
{
"long_name" : "Bedford Avenue",
"short_name" : "Bedford Ave",
"types" :
[
"route"
]
},
{
"long_name" : "Williamsburg",
"short_name" : "Williamsburg",
"types" :
[
"neighborhood",
"political"
]
},
{
"long_name" : "Brooklyn",
"short_name" : "Brooklyn",
"types" :
[
"political",
"sublocality",
"sublocality_level_1"
]
},
{
"long_name" : "Kings County",
"short_name" : "Kings County",
"types" :
[
"administrative_area_level_2",
"political"
]
},
{
"long_name" : "New York",
"short_name" : "NY",
"types" :
[
"administrative_area_level_1",
"political"
]
},
{
"long_name" : "United States",
"short_name" : "US",
"types" :
[
"country",
"political"
]
},
{
"long_name" : "11211",
"short_name" : "11211",
"types" :
[
"postal_code"
]
},
{
"long_name" : "4230",
"short_name" : "4230",
"types" :
[
"postal_code_suffix"
]
}
],
"formatted_address" : "281 Bedford Ave, Brooklyn, NY 11211, USA",
"geometry" :
{
"bounds" :
{
"northeast" :
{
"lat" : 40.7142054,
"lng" : -73.9612142
},
"southwest" :
{
"lat" : 40.7140652,
"lng" : -73.9614433
}
},
"location" :
{
"lat" : 40.7141354,
"lng" : -73.9613287
},
"location_type" : "ROOFTOP",
"viewport" :
{
"northeast" :
{
"lat" : 40.71548428029149,
"lng" : -73.9599797697085
},
"southwest" :
{
"lat" : 40.7127863197085,
"lng" : -73.9626777302915
}
}
},
"navigation_points" :
[
{
"location" :
{
"latitude" : 40.7141769,
"longitude" : -73.9614164
}
}
],
"place_id" : "ChIJiYRKQWBZwokR10UtO7vMvr0",
"types" :
[
"premise",
"street_address"
]
},
{
"address_components" :
[
{
"long_name" : "277",
"short_name" : "277",
"types" :
[
"street_number"
]
},
{
"long_name" : "Bedford Avenue",
"short_name" : "Bedford Ave",
"types" :
[
"route"
]
},
{
"long_name" : "Williamsburg",
"short_name" : "Williamsburg",
"types" :
[
"neighborhood",
"political"
]
},
{
"long_name" : "Brooklyn",
"short_name" : "Brooklyn",
"types" :
[
"political",
"sublocality",
"sublocality_level_1"
]
},
{
"long_name" : "Kings County",
"short_name" : "Kings County",
"types" :
[
"administrative_area_level_2",
"political"
]
},
{
"long_name" : "New York",
"short_name" : "NY",
"types" :
[
"administrative_area_level_1",
"political"
]
},
{
"long_name" : "United States",
"short_name" : "US",
"types" :
[
"country",
"political"
]
},
{
"long_name" : "11211",
"short_name" : "11211",
"types" :
[
"postal_code"
]
}
],
"formatted_address" : "277 Bedford Ave, Brooklyn, NY 11211, USA",
"geometry" :
{
"location" :
{
"lat" : 40.7142205,
"lng" : -73.9612903
},
"location_type" : "ROOFTOP",
"viewport" :
{
"northeast" :
{
"lat" : 40.71556948029149,
"lng" : -73.95994131970849
},
"southwest" :
{
"lat" : 40.7128715197085,
"lng" : -73.9626392802915
}
}
},
"navigation_points" :
[
{
"location" :
{
"latitude" : 40.7142199,
"longitude" : -73.9613932
}
}
],
"place_id" : "ChIJIdIK_DJZwokRImC6xolwWOM",
"plus_code" :
{
"compound_code" : "P27Q+MF Brooklyn, NY, USA",
"global_code" : "87G8P27Q+MF"
},
"types" :
[
"establishment",
"food",
"point_of_interest",
"restaurant"
]
},
{
"address_components" :
[
{
"long_name" : "294",
"short_name...
curl --location --request GET 'https://zylalabs.com/api/9129/reverse+geocode+data+api/16516/reverse+geocoding?latlng=40.714222,-73.961442' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint, you must specify an address in the parameter.
Geocoding - Características del Endpoint
| Objeto | Descripción |
|---|---|
address |
[Requerido] Indicate an address |
{
"results" :
[
{
"address_components" :
[
{
"long_name" : "Infinite Loop 1",
"short_name" : "Infinite Loop 1",
"types" :
[
"premise"
]
},
{
"long_name" : "1",
"short_name" : "1",
"types" :
[
"street_number"
]
},
{
"long_name" : "Infinite Loop",
"short_name" : "Infinite Loop",
"types" :
[
"route"
]
},
{
"long_name" : "Cupertino",
"short_name" : "Cupertino",
"types" :
[
"locality",
"political"
]
},
{
"long_name" : "Santa Clara County",
"short_name" : "Santa Clara County",
"types" :
[
"administrative_area_level_2",
"political"
]
},
{
"long_name" : "California",
"short_name" : "CA",
"types" :
[
"administrative_area_level_1",
"political"
]
},
{
"long_name" : "United States",
"short_name" : "US",
"types" :
[
"country",
"political"
]
},
{
"long_name" : "95014",
"short_name" : "95014",
"types" :
[
"postal_code"
]
},
{
"long_name" : "2083",
"short_name" : "2083",
"types" :
[
"postal_code_suffix"
]
}
],
"formatted_address" : "Infinite Loop 1, 1 Infinite Loop, Cupertino, CA 95014, USA",
"geometry" :
{
"bounds" :
{
"northeast" :
{
"lat" : 37.3321786,
"lng" : -122.0297996
},
"southwest" :
{
"lat" : 37.3312158,
"lng" : -122.0305776
}
},
"location" :
{
"lat" : 37.3318598,
"lng" : -122.0302485
},
"location_type" : "ROOFTOP",
"viewport" :
{
"northeast" :
{
"lat" : 37.3330203302915,
"lng" : -122.0289492197085
},
"southwest" :
{
"lat" : 37.3303223697085,
"lng" : -122.0316471802915
}
}
},
"navigation_points" :
[
{
"location" :
{
"latitude" : 37.33116529999999,
"longitude" : -122.0307429
},
"restricted_travel_modes" :
[
"WALK"
]
},
{
"location" :
{
"latitude" : 37.3314215,
"longitude" : -122.030747
}
},
{
"location" :
{
"latitude" : 37.3317064,
"longitude" : -122.0307154
}
},
{
"location" :
{
"latitude" : 37.3319324,
"longitude" : -122.0307347
}
}
],
"place_id" : "ChIJAf9D3La1j4ARuwKZtGjgMXw",
"types" :
[
"premise",
"street_address"
]
}
],
"status" : "OK"
}
curl --location --request GET 'https://zylalabs.com/api/9129/reverse+geocode+data+api/16517/geocoding?address=1 Infinite Loop, Cupertino, CA 95014, USA' --header 'Authorization: Bearer YOUR_API_KEY'
| Encabezado | Descripción |
|---|---|
Autorización
|
[Requerido] Debería ser Bearer access_key. Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito. |
Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.
The Reverse Geocoding endpoint returns structured geographic information based on latitude and longitude coordinates. This includes a formatted address, address components (like street number, neighborhood, city, state, and postal code), precise coordinates, location type, viewport for mapping, and Plus codes.
Key fields in the response include `formatted_address`, `address_components`, `geometry.location` (with latitude and longitude), `location_type`, `viewport`, and `plus_code`. Each field provides specific geographic details for accurate location identification.
The response data is organized into a JSON structure. The main components include a `formatted_address` string, an array of `address_components` detailing each address part, a `geometry` object containing location coordinates, and a `plus_code` for alternative location representation.
The Geocoding endpoint provides information based on a specified address, returning structured data similar to the Reverse Geocoding endpoint. This includes the formatted address, address components, coordinates, and Plus codes, allowing users to convert addresses into geographic data.
Users can customize their requests by specifying latitude and longitude for the Reverse Geocoding endpoint or an address for the Geocoding endpoint. Additional parameters may include language preferences or specific data formats, depending on the API's capabilities.
The data is sourced from a combination of authoritative geographic databases, mapping services, and user-contributed information. This multi-source approach helps ensure comprehensive coverage and accuracy of geographic details.
Typical use cases include geolocation applications, logistics and delivery services, address validation, territory analysis, and geographic information systems (GIS). The API is useful for any application requiring precise location data and structured address information.
If the API returns partial or empty results, users should check the input coordinates for accuracy. Additionally, consider implementing fallback mechanisms, such as querying nearby locations or using alternative data sources to enhance result completeness.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Nivel de Servicio:
100%
Tiempo de Respuesta:
288ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
582ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1,770ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
288ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
929ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
642ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
288ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
775ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
288ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1,191ms
Registro gratuito
