About the API:
Reverse geocoding is the process of assigning, based on known geographic coordinates, a physical address, or a place name. This process allows the identification of postal addresses, places or territorial subdivisions such as towns, neighborhoods, postal codes, municipalities, provinces, or countries from a pair of XY coordinates. For this reason, reverse geocoding is the opposite process to geocoding, in which from given coordinates we obtain the textual physical address of the elements we want.
This API will receive latitude and longitude of your choice, and it will deliver location information.
Fleet Tracking
Any organization that controls a fleet of vehicles, be they city buses, delivery vans, or cruise ships, needs a system that can keep track of where each unit is at any given time.
Delivery Tracking
Often alongside fleet tracking, e-commerce and supply chain organizations must track an ever-changing network of individual deliveries. In order to keep the operation running smoothly, employees need to be aware of which deliveries are on time, which are running behind, and which have gone missing.
Internet of Things
Reverse geocoders can also help us with the increasing number of smart devices we use in our daily lives. Tablets, watches, cars, fridges, and many other devices now come equipped with f cameras and sensors. More and more devices are location-enabled, capturing real-time locations' GPS coordinates. The internet of things is an incredibly independent network, meaning its operation relies heavily on the continuous input of tracking data from these sensors.
Many people now wear fitness trackers, not just at the gym, but everywhere they go. Reverse geocoding could help them make sense of their daily schedule.
Photo and Data Enrichment
Location-aware social media culture has forever changed the way photos are shared and stored. Alongside each new photograph a smartphone captures, it stores the geographic coordinates where that photograph was taken. This can be useful for enhanced social media sharing, organizing databases full of images, or creating hot maps with access to photographs like Google Maps offers.
In these cases, a reverse geocoder would be necessary if location information needed to be displayed to users.
Payment Processing
As web services become more globalized and their access stretches across national boundaries, their jobs get more complex. For each nation your service operates in, your website needs to be able to convert prices to both shows and collect the right amount for a transaction. If your website displays your products with dollar values in the United Kingdom, you will be undercharging your customers relative to the rate of exchange and losing money in the process. The right reverse geocoding API can gather a customer's location information and convert all values displayed on their web page to local currency.
Besides API call limitations per month, there are no other limitations.
Provide latitude and longitude coordinates in the "lat" and "lon" parameters to get the corresponding address back.
Location To Address - Endpoint Features
Object | Description |
---|---|
latitude |
[Required] |
longitude |
[Required] |
{"success":true,"full_address":"Spruce Avenue, Woodland, Cowlitz County, Washington, 98674, United States","city":"","state":"Washington","country":"United States"}
curl --location --request GET 'https://zylalabs.com/api/751/reverse+geocoding+api/468/location+to+address?latitude=45.523491&longitude=-122.623095' --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.
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]
Service Level:
100%
Response Time:
1,770ms
Service Level:
100%
Response Time:
760ms
Service Level:
100%
Response Time:
340ms
Service Level:
100%
Response Time:
1,365ms
Service Level:
100%
Response Time:
1,191ms
Service Level:
100%
Response Time:
1,436ms
Service Level:
100%
Response Time:
715ms
Service Level:
100%
Response Time:
1,246ms
Service Level:
100%
Response Time:
2,088ms
Service Level:
50%
Response Time:
2,089ms
Service Level:
100%
Response Time:
689ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
127ms
Service Level:
100%
Response Time:
628ms
Service Level:
100%
Response Time:
680ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
1,399ms