Address Conversion API

Address Conversion API transforms human-readable addresses into precise geographic coordinates, facilitating accurate mapping, navigation, and location-based services.

About the API:  

Direct and inverse geocoding are essential processes in modern mapping and location services, as they allow us to bridge the gap between easy-to-understand location descriptions and precise geographic coordinates. These two interconnected techniques enable accurate mapping and navigation, as well as the development of location-aware applications.

Direct geocoding is the process of converting human-readable location information, such as addresses or place names, into geographic coordinates, specifically latitude and longitude. This transformation enables computers and mapping systems to effectively understand and interpret location data. The API's direct geocoding service takes addresses or place names entered by the user and compares them to corresponding geographic coordinates on the Earth's surface. This technology plays a crucial role in the navigation applications we rely on every day, as well as in e-commerce platforms that need to accurately display nearby stores or services.

Reverse geocoding is the counterpart of direct geocoding, and consists of converting geographic coordinates back into human-readable location information. This technique is particularly valuable for mapping applications, where the location of a particular place on the map can provide users with contextual information about nearby landmarks, addresses and points of interest. The API's reverse geocoding service allows users to obtain meaningful location descriptions based on coordinates.

The Address Conversion API provides users with a robust and easy-to-use platform for implementing direct and reverse geocoding functionality. With our well-documented API, users can seamlessly incorporate these features into their applications, improving their overall usability and value.

Both direct and reverse geocoding rely on an extensive location database. This database includes a wide range of geographic features, such as streets, landmarks, neighborhoods and cities. As a user or developer, you can leverage this rich repository to translate between human-readable addresses and precise coordinates with high accuracy.

In conclusion, direct and reverse geocoding, powered by the Address Conversion API, form the foundation of modern mapping and location services. These techniques seamlessly translate human-readable location information and precise geographic coordinates, enabling a myriad of applications that affect our daily lives. Whether it's navigating unfamiliar streets, ordering food or analyzing market trends, the accuracy and versatility of direct and inverse geocoding continue to shape our interconnected world.

 

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. Map annotations: Mobile apps or web platforms that allow users to place pushpins or markers on maps benefit from reverse geocoding, which can provide them with accurate descriptions of the location of those markers.

  2. Fitness and health apps: Applications that record users' exercise routes or walks can provide context by converting recorded GPS coordinates into recognizable addresses.

  3. Location-based social networking: Social networking platforms use reverse geocoding to attach location tags to users' posts and photos, allowing them to share their experiences more effectively.

  4. Real estate and property listings: When users search for properties, reverse geocoding can transform the latitude and longitude of each listing into a user-friendly address, which helps identify the property.

  5. Weather services: Weather applications use reverse geocoding to provide localized forecasts, ensuring that users receive accurate weather information specific to their current or chosen location.

Are there any limitations to your plans?

  • Basic Plan: 3,000 API Calls. 2000 requests per second.

  • Pro Plan: 9,000 API Calls. 2000 requests per second.

  • Pro Plus Plan: 27,000 API Calls. 2000 requests per second.

  • Premium Plan: 81,000 API Calls. 2000 requests per second.

API Documentation

Endpoints


To use this endpoint all you have to do is enter a latitude and longitude in the parameter.



                                                                            
GET https://www.zylalabs.com/api/2409/address+conversion+api/2339/reverse+geocode
                                                                            
                                                                        

Reverse geocode - Endpoint Features

Object Description
lon [Required]
lat [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"success":true,"code":200,"data":{"address":"520 S Michigan Ave, Chicago, IL 60605, Hoa Kα»³","province":"60605"}}
                                                                                                                                                                                                                    
                                                                                                    

Reverse geocode - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/2409/address+conversion+api/2339/reverse+geocode?lon=-87.6244212&lat=41.8755616' --header 'Authorization: Bearer YOUR_API_KEY' 

    

To use this endpoint all you have to do is enter an address in the parameter.



                                                                            
GET https://www.zylalabs.com/api/2409/address+conversion+api/2340/forward+geocode
                                                                            
                                                                        

Forward geocode - Endpoint Features

Object Description
query [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"success":true,"code":200,"data":[{"boundingbox":["41.644531","42.0230396","-87.940101","-87.5240812"],"lat":"41.8755616","lon":"-87.6244212","display_name":"Chicago, Cook County, Illinois, United States","place_rank":16,"category":"boundary","type":"administrative","importance":0.8515295727100248,"icon":"https://nominatim.openstreetmap.org/ui/mapicons/poi_boundary_administrative.p.20.png"},{"boundingbox":["42.1422982","42.1455099","-87.7992098","-87.7971537"],"lat":"42.1455099","lon":"-87.7992098","display_name":"Chicago, North Shore & Milwaukee, Henrici Drive, Northbrook, Northfield Township, Cook County, Illinois, 60082, United States","place_rank":30,"category":"railway","type":"abandoned","importance":0.4243522234962407},{"boundingbox":["42.1459209","42.1475949","-87.8006125","-87.7995211"],"lat":"42.1472393","lon":"-87.8003803","display_name":"Chicago, North Shore & Milwaukee, Edens Spur, Williamsburg Square, Northfield Township, Cook County, Illinois, 60082, United States","place_rank":30,"category":"railway","type":"abandoned","importance":0.4243522234962407},{"boundingbox":["42.1455099","42.1459209","-87.7995211","-87.7992098"],"lat":"42.1459209","lon":"-87.7995211","display_name":"Chicago, North Shore & Milwaukee, Edens Spur, Lee Acres, Northbrook, Northfield Township, Cook County, Illinois, 60082, United States","place_rank":30,"category":"railway","type":"abandoned","importance":0.4243522234962407},{"boundingbox":["41.8914706","41.9014706","-87.6407194","-87.6307194"],"lat":"41.8964706","lon":"-87.6357194","display_name":"Chicago, 300, West Chicago Avenue, River North, Chicago, Cook County, Illinois, 60654, United States","place_rank":30,"category":"railway","type":"station","importance":0.3960833436228193,"icon":"https://nominatim.openstreetmap.org/ui/mapicons/transport_train_station2.p.20.png"},{"boundingbox":["41.8916529","41.9016529","-87.6331533","-87.6231533"],"lat":"41.8966529","lon":"-87.6281533","display_name":"Chicago, 800, North State Street, Magnificent Mile, Near North Side, Chicago, Cook County, Illinois, 60654, United States","place_rank":30,"category":"railway","type":"station","importance":0.3885709817044999,"icon":"https://nominatim.openstreetmap.org/ui/mapicons/transport_train_station2.p.20.png"},{"boundingbox":["41.8911978","41.9011978","-87.6603579","-87.6503579"],"lat":"41.8961978","lon":"-87.6553579","display_name":"Chicago, 800, North Milwaukee Avenue, West Town, Chicago, West Chicago Township, Cook County, Illinois, 60642, United States","place_rank":30,"category":"railway","type":"station","importance":0.3868347429646153,"icon":"https://nominatim.openstreetmap.org/ui/mapicons/transport_train_station2.p.20.png"},{"boundingbox":["-33.73745","-33.69745","18.9763167","19.0163167"],"lat":"-33.71745","lon":"18.9963167","display_name":"Chicago, Drakenstein Ward 24, Paarl, Drakenstein Local Municipality, Cape Winelands District Municipality, Western Cape, 7646, South Africa","place_rank":19,"category":"place","type":"suburb","importance":0.375,"icon":"https://nominatim.openstreetmap.org/ui/mapicons/poi_place_village.p.20.png"},{"boundingbox":["-18.9735788","-18.9335788","29.7753081","29.8153081"],"lat":"-18.9535788","lon":"29.7953081","display_name":"Chicago, Kwekwe, Midlands, Zimbabwe","place_rank":19,"category":"place","type":"suburb","importance":0.375,"icon":"https://nominatim.openstreetmap.org/ui/mapicons/poi_place_village.p.20.png"},{"boundingbox":["41.6534151","41.6535644","-91.5341831","-91.5336817"],"lat":"41.6534745","lon":"-91.53393237502479","display_name":"Chicago, Rock Island and Pacific Railroad Passenger Station, Wright Street, Iowa City, Johnson County, Iowa, 52240, United States","place_rank":30,"category":"historic","type":"building","importance":0.3745321115064417}]}
                                                                                                                                                                                                                    
                                                                                                    

Forward geocode - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/2409/address+conversion+api/2340/forward+geocode?query=chicago' --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 Address Conversion API REST API, simply include your bearer token in the Authorization header.
Headers
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

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.

The Address Conversion API converts readable addresses into exact geographic coordinates, enabling precise mapping, navigation, and location-based services.

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

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
1,246ms

Category:


Related APIs