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.

API description

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://www.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://www.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 plan for small amount of requests per day, but it’s rate is limit to prevent abuse of the service.

Sure, you can use it and pay only when you use it. The credit can’t be expired.

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, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.

Prices are listed in USD. 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 with paying by card, just contact us at [email protected]

Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further

Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.

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.

Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.

Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.

You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]

 Service Level
 Response Time



Related APIs