The Mountain Peaks Data API is designed to handle data specifically related to the highest mountain peaks on Earth, focusing on their elevation above sea level and geographical distribution. The API processes various data fields, including mountain names, heights (in meters or feet), geographical coordinates (latitude and longitude), and associated countries or regions. It adheres to geographical data standards and formats, ensuring compatibility with GIS applications and mapping services. The API supports queries for retrieving lists of mountains, detailed information about specific peaks, and geographical distribution data. Technical requirements include adherence to RESTful principles, with responses formatted in JSON for easy integration into web applications. The output schema includes structured data fields for mountain attributes, ensuring clarity and ease of use for developers. This API is essential for researchers, geographers, and outdoor enthusiasts interested in mountain data and geography.
[
{
"names": [
"Mount Everest",
"K2",
"Kangchenjunga",
"Lhotse",
"Makalu",
"Cho Oyu",
"Dhaulagiri I",
"Manaslu",
"Nanga Parbat",
"Annapurna I",
"Gasherbrum I",
"Broad Peak",
"Gasherbrum II",
"Shishapangma",
"Gyachung Kang",
"Gasherbrum III",
"Annapurna II",
"Gasherbrum IV",
"Himalchuli",
"Distaghil Sar",
"Ngadi Chuli",
"Nuptse",
"Khunyang Chhish",
"Masherbrum",
"Nanda Devi",
"Chomo Lonzo",
"Batura Sar",
"Rakaposhi",
"Namcha Barwa",
"Kanjut Sar",
"Kamet",
"Dhaulagiri II",
"Saltoro Kangri",
"Kumbhakarna",
"Tirich Mir",
"Molamenqing",
"Gurla Mandhata",
"Saser Kangri I",
"Chogolisa",
"Dhaulagiri IV",
"Kongur Tagh",
"Dhaulagiri V",
"Shispare",
"Trivor",
"Gangkhar Puensum",
"Gongga Shan",
"Annapurna III",
"Skyang Kangri",
"Changtse",
"Kula Kangri",
"Kongur Tiube",
"Annapurna IV",
"Mamostong Kangri",
"Saser Kangri II E",
"Muztagh Ata",
"Ismoil Somoni Peak",
"Saser Kangri III",
"Noshaq",
"Pumari Chhish",
"Passu Sar",
"Yukshin Gardan Sar",
"Teram Kangri I",
"Jongsong Peak",
"Malubiting",
"Gangapurna",
"Jengish Chokusu",
"Sunanda Devi",
"K12",
"Yangra",
"Sia Kangri",
"Momhil Sar",
"Kabru N",
"Skil Brum",
"Haramosh Peak",
"Istor-o-Nal",
"Ghent Kangri",
"Ultar",
"Rimo I",
"Churen Himal",
"Teram Kangri III",
"Sherpi Kangri",
"Labuche Kang",
"Kirat Chuli",
"Abi Gamin",
"Gimmigela Chuli",
"Nangpai Gosum",
"Saraghrar",
"Talung",
"Jomolhari",
"Chamlang",
"Chongtar",
"Baltoro Kangri",
"Siguang Ri",
"The Crown",
"Gyala Peri",
"Porong Ri",
"Baintha Brakk",
"Yutmaru Sar",
"K6",
"Kangpenqing",
"Muztagh Tower",
"Mana Peak",
"Dhaulagiri VI",
"Diran",
"Labuche Kang III",
"Putha Hiunchuli",
"Apsarasas Kangri",
"Mukut Parbat",
"Rimo III",
"Langtang Lirung",
"Karjiang",
"Annapurna Dakshin",
"Khartaphu",
"Tongshanjiabu",
"Malangutti Sar",
"Noijin Kangsang",
"Langtang Ri",
"Kangphu Kang",
"Singhi Kangri",
"Lupghar Sar"
]
}
]
curl --location --request POST 'https://zylalabs.com/api/8842/mountain+peaks+data+api/15581/get+all+mountain+names' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"name": "K2",
"rank": 2,
"height_rounded": 8611,
"prominence_rounded": 4020,
"range": "Baltoro Karakoram",
"coordinates": "35°52′53″N 76°30′48″E / 35.88139°N 76.51333°E / 35.88139; 76.51333 (2. K2 / Qogir / Godwin Austen (8611 m))",
"parent_mountain": "Mount Everest",
"first_ascent": 1954,
"country": "Pakistan, China"
}
]
curl --location --request POST 'https://zylalabs.com/api/8842/mountain+peaks+data+api/15582/get+mountain+data+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"name":"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.
The API provides comprehensive data on the highest mountain peaks, including mountain names, heights (in meters or feet), geographical coordinates (latitude and longitude), and associated countries or regions.
The API returns data in JSON format, which is structured for easy integration into web applications and adheres to RESTful principles.
The API can be used by researchers, geographers, and outdoor enthusiasts for various applications, such as mapping mountain distributions, studying geographical data, and enhancing outdoor adventure planning.
The output schema includes structured data fields for mountain attributes such as name, elevation, geographical coordinates, and the country or region where the mountain is located.
Developers can integrate the API by making RESTful queries to retrieve lists of mountains or detailed information about specific peaks, utilizing the structured JSON responses for seamless incorporation into their applications.
This endpoint returns a list of all mountain names in the dataset. The response is structured as a JSON array containing a single object with a "names" field, which includes the names of the highest mountain peaks.
The response includes fields such as "name," "rank," "height_rounded," "prominence_rounded," "range," "coordinates," "parent_mountain," "first_ascent," and "country," providing detailed information about the specified mountain.
Users can customize their requests by specifying the mountain name as a parameter in the API call. This allows them to retrieve detailed information for any mountain listed in the dataset.
The response is organized as a JSON array containing objects, each representing a mountain. Each object includes key-value pairs for various attributes, making it easy to access specific information about the mountain.
This endpoint provides a comprehensive list of mountain names, allowing users to explore the highest peaks globally. It serves as a foundational resource for further queries about specific mountains.
The API sources its data from reputable geographical databases and adheres to geographical data standards. Regular updates and quality checks ensure the accuracy and reliability of the mountain data provided.
Typical use cases include academic research on mountain geography, outdoor adventure planning, GIS mapping projects, and educational purposes for learning about the world's highest peaks and their characteristics.
Users can parse the JSON responses to extract relevant mountain attributes for analysis, visualization, or integration into applications. The structured format allows for easy manipulation and display of mountain data in various contexts.
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:
71ms
Service Level:
100%
Response Time:
12,201ms
Service Level:
100%
Response Time:
17,043ms
Service Level:
100%
Response Time:
3,924ms
Service Level:
100%
Response Time:
2,244ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
1,873ms
Service Level:
100%
Response Time:
61ms
Service Level:
100%
Response Time:
1,527ms
Service Level:
100%
Response Time:
4,899ms
Service Level:
100%
Response Time:
373ms
Service Level:
100%
Response Time:
600ms
Service Level:
100%
Response Time:
597ms
Service Level:
100%
Response Time:
1,145ms
Service Level:
100%
Response Time:
657ms
Service Level:
100%
Response Time:
583ms
Service Level:
100%
Response Time:
353ms
Service Level:
100%
Response Time:
22ms
Service Level:
100%
Response Time:
709ms
Service Level:
100%
Response Time:
756ms