Location Translation API

Location Translation API

The Location Translation API seamlessly translates addresses to coordinates (Forward) and coordinates to addresses (Reverse), enhancing location-based applications' accuracy and functionality.

About the API:  

In the intricate world of location-based services, the Location Translation API is an indispensable tool that enables users to bridge the gap between geographic coordinates and human-readable addresses. Through precise algorithms and seamless integration, this API enables applications and platforms to deliver meaningful location-based experiences to users, from locating exact addresses to mapping routes and destinations.

The API takes latitude and longitude coordinates and quickly translates them into readable addresses. This feature is invaluable when users need to convert raw geographic data into understandable locations, whether for navigation purposes, tracking deliveries or enhancing user profiles with location details.

In contrast, the Location Translation API performs the reverse process. It takes textual addresses or place names and translates them into precise latitude and longitude coordinates. This capability allows applications to display locations on maps, helping users visualize their destinations, find nearby points of interest or set up geofences for location-based notifications.

Incorporating the Location Translation API into applications is a strategic move for any user who wants to improve the user experience and extend the utility of their platforms. In the case of navigation apps, it allows users to enter destination names, retrieve precise coordinates and seamlessly plot routes. Location-based social platforms can add context to user-generated content, enriching posts with location data. E-commerce services can optimize delivery routes, providing customers with real-time tracking information.

A notable advantage of this API is its versatility. It supports various geodata formats and international addressing systems, allowing developers to create global applications without having to deal with location-specific complexities.

Integration into applications is facilitated by its comprehensive documentation and endpoints, allowing users to streamline the deployment process. Whether on web platforms, mobile apps or IoT devices, seamless integration transforms raw geographic data into understandable and actionable information.

In conclusion, the Location Translation API represents a major breakthrough in the field of location-based services. Its ability to seamlessly translate between coordinates and addresses transforms raw data into valuable information, giving users the means to enrich applications with contextual information. As the world continues to embrace location-based technology, this API is emerging as an indispensable tool, bridging the gap between geographic data and human understanding, ultimately enhancing the user experience and expanding the horizons of digital innovation.


What this API receives and what your API provides (input/output)?

It will receive parameters and provide you with a JSON.


What are the most common uses cases of this API?

  1. Navigation applications: Direct geocoding allows users to enter addresses or place names, while reverse geocoding helps display users' locations on maps, providing seamless navigation and real-time route guidance.

  2. Location-based social networking: Direct geocoding contextualizes user-generated content by converting location names into coordinates and enriching posts with accurate geotags.

  3. E-commerce and delivery services: Direct geocoding optimizes delivery routes by converting customer addresses into coordinates, while reverse geocoding allows users to track deliveries and estimate arrival times.

  4. Travel planning: Direct geocoding helps travelers find accommodations, restaurants and attractions by converting destination names into coordinates, improving travel planning platforms.

  5. Photo geotagging: Reverse geotagging allows users to tag photos with location information, which enhances visual storytelling and helps photographers share the exact locations they have captured.

Are there any limitations to your plans?

  • 1 request per second.

  • Basic Plan: 9,000 API Calls. 300 requests per day and 3 requests per second.

  • Pro Plan: 27,000 API Calls. 900 requests per day and 3 requests per second.

  • Pro Plus Plan: 90,000 API Calls. 3,000 requests per day and 10 request per second.

  • Premium Plan: 450,000 API Calls. 15,000 request per day.

API Documentation


To use this endpoint you must specify an address in the parameter.

GET https://zylalabs.com/api/2429/location+translation+api/2372/location+by+address

Location by address - Endpoint Features
Object Description
address [Required]
Test Endpoint


                                                                                                                                                                                                                            {"results":[{"formatted_address":"Heritage Dr, Wells, Maine, 04090","geometry":{"location":{"lat":43.354669508025,"lng":-70.565021315381}}}],"status":"OK"}

Location by address - CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/2429/location+translation+api/2372/location+by+address?address=4090 Heritage Drive' --header 'Authorization: Bearer YOUR_API_KEY' 


To use this endpoint you must indicate in the parameter the latitude and longitude of an address.

GET https://zylalabs.com/api/2429/location+translation+api/2373/location+by+coordinates

Location by coordinates - Endpoint Features
Object Description
latlng [Required]
Test Endpoint



Location by coordinates - CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/2429/location+translation+api/2373/location+by+coordinates?latlng=36.778259,-119.417931' --header 'Authorization: Bearer YOUR_API_KEY' 


API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Location Translation API REST API, simply include your bearer token in the Authorization header.


Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise
Starts at
$ 10,000/Year

  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

To use this API the user must enter a longitude and latitude or an address.

There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.

Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.

It is an API that provides users with information based on reverse and inverse geocoding.

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
 Response Time


Related APIs