The Elevation Data API provides accurate elevation data for specific geographic coordinates, making it beneficial for numerous applications, including outdoor navigation, environmental research, urban planning, and scientific investigations. By supplying precise elevation information, the API significantly enhances the functionality and accuracy of location-based services.
Users can obtain elevation data by submitting a pair of geographic coordinates defined by latitude and longitude. The API processes these inputs and delivers detailed information about the elevation at the specified location. The response includes essential data points such as the elevation value, exact coordinates, measurement resolution, and the status of the request.
Moreover, the API response features a location object that specifies the latitude and longitude tied to the elevation data. This ensures that the returned elevation accurately corresponds to the provided coordinates, ensuring data reliability. The location information is also useful for mapping or visualization, as it enables users to identify the precise spots where elevation data was gathered.
In conclusion, the Elevation Data API serves as a powerful solution for retrieving accurate elevation data based on geographic coordinates. Its comprehensive output—including elevation values, location specifics, resolution, and status—makes it a versatile tool across various fields. As the demand for location-based services continues to rise, the Elevation Data API remains an essential resource for those seeking dependable elevation data for their projects and research.
To use this endpoint you must indicate a latitude and longitude in the parameter.
Elevation by coordinates - Endpoint Features
Object | Description |
---|---|
locations |
[Required] Indicates a latitude and longitude as (39.7391536,-104.9847034) |
{
"results" :
[
{
"elevation" : 1608.637939453125,
"location" :
{
"lat" : 39.7391536,
"lng" : -104.9847034
},
"resolution" : 4.771975994110107
}
],
"status" : "OK"
}
curl --location --request GET 'https://zylalabs.com/api/5222/elevation+data+api/6689/elevation+by+coordinates?locations=39.7391536,-104.9847034' --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.
To use this API users must indicate a latitude and longitude.
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.
The Elevation Data API receives latitude and longitude as input and provides elevation data, location details, resolution, and a success status.
Besides the number of API calls per month, there are no other limitations.
The Elevation Data API retrieves elevation data for specified geographic coordinates.
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, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response 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:
94ms
Service Level:
100%
Response Time:
108ms
Service Level:
100%
Response Time:
69ms
Service Level:
100%
Response Time:
447ms
Service Level:
100%
Response Time:
396ms
Service Level:
100%
Response Time:
13,404ms
Service Level:
100%
Response Time:
849ms
Service Level:
100%
Response Time:
364ms
Service Level:
100%
Response Time:
493ms
Service Level:
100%
Response Time:
467ms
Service Level:
100%
Response Time:
347ms
Service Level:
83%
Response Time:
1,219ms
Service Level:
100%
Response Time:
286ms
Service Level:
100%
Response Time:
1,010ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
624ms
Service Level:
100%
Response Time:
87ms