Location Identification API

Location Identification API is commonly used in applications that require location-based services, such as navigation, asset tracking, and emergency response systems.

About the API:  


The Location Identification API is a web service that allows developers to convert latitude and longitude coordinates into readable location descriptions. The API can be used to obtain various information about a location, such as address, city, state and country. It can also provide details such as zip codes or neighborhood names.

Inverse geocoding is the process of obtaining an address or location description from a set of geographic coordinates. It is a useful tool for mapping applications and services that require location-based information. Reverse geocoding can be performed using several APIs, including the Reverse Geocoding API.

Location Identification API uses geocoding algorithms to match the entered coordinates to a location in a database.

Using the Location Identification API is usually a straightforward process. Developers can integrate the API into their applications using simple RESTful requests. The API requires input parameters, such as latitude and longitude coordinates. Once the request is made, the API returns a response in the form of a structured JSON object. This response contains the location information retrieved from the database.

One of the advantages of using this API is its versatility. The API can be used in a variety of applications, such as navigation systems, weather applications and social networking platforms. It can also be used in conjunction with other APIs, such as mapping and routing APIs, to provide a complete location-based service.

Another advantage of the Location Identification API is its accuracy. The API uses advanced geocoding algorithms and multiple data sources to ensure that the location information it returns is as accurate as possible. This accuracy can be especially important in applications that require precise location information, such as emergency response systems and asset tracking systems. .

In short, it is a powerful tool for obtaining location information from geographic coordinates. It is easy to use, versatile and accurate, making it a valuable resource for developers and businesses that rely on location data.

 

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. Real-time location services: Can be used in real-time location-based services, such as ridesharing applications, to quickly determine the nearest pick-up and drop-off address or landmark.

  2. Asset tracking: Can be used in asset tracking systems to provide asset location description.

  3. Emergency response: Reverse geocoding APIs can be used in emergency response systems to quickly obtain the address or location description of a caller for faster dispatch of emergency services.

  4. Business intelligence: They can be used in business intelligence applications to provide customer location information, which helps companies make better marketing and product placement decisions.

  5. Weather and environmental monitoring: Can be used in weather and environmental monitoring systems to identify the location of weather stations and environmental sensors.


Are there any limitations to your plans?

2 requests per second.

Basic Plan: 100,000 API Calls. 10 requests per second.

Pro Plan: 250,000 API Calls. 20 requests per second.

Pro Plus Plan: 1,000,000 API Calls. 40 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://zylalabs.com/api/2016/location+identification+api/1788/get+location
                                                                            
                                                                        

Get Location - Endpoint Features

Object Description
location [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"results":[{"address":"123 Victoria St, London SW1E 6DE, UK","postal_code":"SW1E 6DE","country":"United Kingdom","region":"England","area":"Greater London","street":"Victoria Street","house":"123","location":{"lat":51.507346,"lng":-0.127662},"location_type":"exact","type":"street_address"},{"address":"United Kingdom, London, ヒースロー空港","country":"United Kingdom","region":"England","area":"Greater London","locality":"London","location":{"lat":51.507357,"lng":-0.127774},"location_type":"centroid","type":"poi"},{"address":"3 Whitehall, London SW1A 2DD, UK","postal_code":"SW1A 2DD","country":"United Kingdom","region":"England","area":"Greater London","street":"Whitehall","house":"3","location":{"lat":51.507125,"lng":-0.127218},"location_type":"exact","type":"street_address"},{"address":"GV4C+VX London, UK","country":"United Kingdom","region":"England","area":"Greater London","location":{"lat":51.507204,"lng":-0.127615},"location_type":"centroid","type":"poi"},{"address":"Whitehall, London SW1, UK","postal_code":"SW1","country":"United Kingdom","region":"England","area":"Greater London","street":"Whitehall","location":{"lat":51.507065,"lng":-0.12743},"location_type":"centroid","type":"route"}]}
                                                                                                                                                                                                                    
                                                                                                    

Get Location - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/2016/location+identification+api/1788/get+location?location=51.5072,-0.1276' --header 'Authorization: Bearer YOUR_API_KEY' 

    

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



                                                                            
GET https://zylalabs.com/api/2016/location+identification+api/1789/get+location+by+text
                                                                            
                                                                        

Get Location by text - Endpoint Features

Object Description
address [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"results":[{"address":"48 Leicester Square, London WC2H 7DH, UK","postal_code":"WC2H 7DH","country":"United Kingdom","region":"England","area":"Greater London","street":"Leicester Square","house":"48","location":{"lat":51.510204,"lng":-0.130908},"location_type":"exact","type":"street_address"}]}
                                                                                                                                                                                                                    
                                                                                                    

Get Location by text - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/2016/location+identification+api/1789/get+location+by+text?address=48 Leicester Square' --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 Identification 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

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
389ms

Category:


Related APIs