The Google Geocoding API is a powerful tool that allows developers to convert addresses into geographic coordinates (latitude and longitude) and vice versa. It is part of the comprehensive set of services offered by Google Maps, designed to provide accurate and reliable geolocation data for applications and websites.
With the Google Geocoding API, developers can easily integrate geocoding capabilities into their applications, allowing them to take advantage of the vast amount of geographic data available through Google Maps. The API provides a simple, standardized way to convert addresses to geographic coordinates, making it easier to map locations and improve the overall user experience.
One of the main uses of the geocoding API is address validation. By passing an address as a parameter to the API, developers can obtain the corresponding latitude and longitude coordinates. This feature helps ensure the accuracy and correctness of addresses submitted by users, avoiding errors and improving data integrity.
The Google Geocoding API supports various address formats such as street addresses or latitude and longitude. It also supports international addresses, allowing developers to seamlessly handle geocoding requests from around the world. This global coverage makes it a versatile tool for applications with an international user base or requiring geolocation data in different regions.
This API integrates seamlessly with other Google Maps services, such as the Address API and the Places API. This integration allows developers to create end-to-end mapping solutions by combining geocoding with directions, distance calculation and place search functions.
In addition to address validation, the Google Geocoding API offers reverse geocoding capabilities. By providing latitude and longitude coordinates, developers can obtain detailed information about the corresponding address. This feature is especially useful in situations where precise location information is needed.
It will receive parameters and provide you with a JSON.
Address Verification: Validate and verify user-entered addresses by converting them into accurate geographic coordinates. This ensures data accuracy and improves the user experience.
Location-based services: Create location-based applications and services that use the API to determine a user's location and provide relevant information, such as nearby points of interest, local businesses or personalized recommendations.
Asset tracking: Track the real-time position of vehicles, assets or shipments by converting GPS coordinates into meaningful addresses. This enables efficient logistics management and enhances tracking capabilities.
Distance calculation: Calculate distances between multiple addresses or coordinates to determine travel times, optimize routes or generate proximity-based search results. This is very useful for navigation applications, delivery services or trip planning.
Reverse geocoding: Obtain detailed address information from latitude and longitude coordinates. This can be used to display place names based on the user's position.
Besides the number of API calls, there is no other limitation.
To use this endpoint, all you have to do is provide the street address you wish to geocode using the format accepted by the national postal service of the country concerned.
Get geocoding - Endpoint Features
Object | Description |
---|---|
address |
[Required] |
{"address":"Jacarandaes 6207","latitude":"","longitude":"","status":"success"}
curl --location --request GET 'https://zylalabs.com/api/2170/google+geocoding+api/1976/get+geocoding?address=6253 Hollywood LA USA' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint all you have to do is enter a latitude and longitude in the parameters.
Reverse geocode - Endpoint Features
Object | Description |
---|---|
lat |
[Required] |
long |
[Required] |
{"address":"Hollywood, Los Angeles, CA 90028, USA","latitude":"34.101847299999996","longitude":"-118.326292","status":"success"}
curl --location --request GET 'https://zylalabs.com/api/2170/google+geocoding+api/1978/reverse+geocode?lat=34.101847299999996&long=-118.326292' --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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
The API may impose limits to ensure fair use and prevent abuse. Please refer to the API plans for specific details on limitations.
The Google Geocoding API is an API that converts addresses into geographic coordinates (latitude and longitude) and vice versa.
To use the API you will have 2 endpoints for both geocoding and reverse geocoding, where depending on the endpoint you must enter an address or a latitude and longitude.
In the case of geocoding endpoint it will get the latitude and longitude of the inserted address and in the case of reverse geocode, it will get the address through the inserted latitude and longitude.
Yes, you can use the Google Geocoding API for both personal and commercial purposes.
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, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
127ms
Service Level:
50%
Response Time:
2,089ms
Service Level:
100%
Response Time:
2,088ms
Service Level:
100%
Response Time:
715ms
Service Level:
100%
Response Time:
1,399ms
Service Level:
100%
Response Time:
1,770ms
Service Level:
100%
Response Time:
340ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
642ms
Service Level:
100%
Response Time:
680ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
1,191ms
Service Level:
100%
Response Time:
689ms
Service Level:
100%
Response Time:
628ms
Service Level:
100%
Response Time:
1,163ms
Service Level:
100%
Response Time:
1,436ms
Service Level:
100%
Response Time:
1,779ms