The US Mountain Stats API delivers structured, queryable access to data on the tallest mountains across all 50 U.S. states. The API is based on information compiled by World Population Review and provides separate endpoints for each data attribute—mountain name, elevation and much more.
{"states":["Alaska","California","Colorado","Washington","Wyoming","Hawaii","Utah","New Mexico","Nevada","Montana","Idaho","Arizona","Oregon","Texas","South Dakota","North Carolina","Tennessee","New Hampshire","Virginia","Nebraska","New York","Maine","Oklahoma","West Virginia","Georgia","Vermont","Kentucky","Kansas","South Carolina","North Dakota","Massachusetts","Maryland","Pennsylvania","Arkansas","Alabama","Connecticut","Minnesota","Michigan","Wisconsin","New Jersey","Missouri","Iowa","Ohio","Indiana","Illinois","Rhode Island","Mississippi","Louisiana","Delaware","District of Columbia","Florida"]}
curl --location --request POST 'https://zylalabs.com/api/6767/us+mountain+stats+api/10131/get+us+states+with+mountains' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"state":"Washington","location":"Mount Rainier"}
curl --location --request POST 'https://zylalabs.com/api/6767/us+mountain+stats+api/10132/get+tallest+mountain+location+by+state' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"state":"Required"}'
{"state":"Washington","location":"Mount Rainier","highest_elevation":14411}
curl --location --request POST 'https://zylalabs.com/api/6767/us+mountain+stats+api/10133/get+highest+elevation+by+location' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"location":"Required"}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
Each endpoint returns structured data related to U.S. mountains. The "get us states with mountains" endpoint returns a list of states, while "get tallest mountain location by state" provides the tallest mountain's name for a specified state. The "get highest elevation by location" endpoint returns the highest elevation of a specified mountain.
The key fields in the response data include "states" for the list of states, "state" and "location" for the tallest mountain's name, and "highest_elevation" for the elevation of a specified mountain. Each field provides essential information for identifying mountains.
The response data is organized in JSON format. Each endpoint returns a structured object with relevant fields. For example, the response from "get tallest mountain location by state" includes "state" and "location" as key-value pairs, making it easy to parse and utilize.
The API provides information on U.S. states with mountains, the tallest mountain in each state, and the highest elevation of specified mountains. This allows users to access comprehensive mountain data based on state and specific attributes.
The "get tallest mountain location by state" endpoint requires a "state" parameter, while the "get highest elevation by location" endpoint requires a "location" parameter. Users must specify these parameters to retrieve relevant mountain data.
Typical use cases include educational purposes, outdoor planning, geographic research, and tourism. Users can leverage the data to identify the tallest mountains in specific states or to compare elevations for hiking or climbing activities.
The US Mountain Stats API sources its data from World Population Review, which is known for compiling reliable geographic information. Regular updates and quality checks help ensure the accuracy and reliability of the mountain statistics provided.
Users can utilize the returned data by integrating it into applications, visualizations, or reports. For instance, the mountain names and elevations can be used in mapping software or educational content to enhance user engagement with geographic information.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
3,924ms
Service Level:
100%
Response Time:
52ms
Service Level:
100%
Response Time:
71ms
Service Level:
100%
Response Time:
1,873ms
Service Level:
100%
Response Time:
61ms
Service Level:
100%
Response Time:
17,043ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
2,244ms
Service Level:
100%
Response Time:
12,201ms
Service Level:
100%
Response Time:
79ms
Service Level:
100%
Response Time:
56ms
Service Level:
100%
Response Time:
2,040ms
Service Level:
100%
Response Time:
1,197ms
Service Level:
100%
Response Time:
63ms
Service Level:
100%
Response Time:
1,110ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
2,443ms
Service Level:
100%
Response Time:
872ms
Service Level:
100%
Response Time:
3,147ms
Service Level:
100%
Response Time:
3,531ms