{
"cities": [
"Athens",
"Paris",
"St. Louis",
"London",
"Stockholm",
"Berlin",
"Antwerp",
"Chamonix",
"St. Moritz",
"Amsterdam",
"Lake Placid",
"Los Angeles",
"Garmisch-Partenkirchen",
"Sapporo",
"Tokyo",
"Helsinki",
"Cortina d'Ampezzo",
"Melbourne",
"Rome",
"Innsbruck",
"Grenoble",
"Mexico City",
"Munich",
"Montreal",
"Moscow",
"Sarajevo",
"Calgary",
"Seoul",
"Albertville",
"Barcelona",
"Atlanta",
"Sydney",
"Salt Lake City",
"Turin",
"Beijing",
"Vancouver",
"Sochi",
"Rio de Janeiro",
"Pyeongchang",
"Tokyo",
"Paris",
"Milan",
"Cortina d'Ampezzo",
"Los Angeles",
"French Alps",
"Brisbane",
"Salt Lake City"
]
}
curl --location --request POST 'https://zylalabs.com/api/10229/olympic+cities+information+extractor+api/19679/get+olympic+games+host+cities' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"country": "United Kingdom",
"city": "London",
"year": 1908
},
{
"country": "United Kingdom",
"city": "London",
"year": 1948
},
{
"country": "United Kingdom",
"city": "London",
"year": 2012
}
]
curl --location --request POST 'https://zylalabs.com/api/10229/olympic+cities+information+extractor+api/19684/get+host+city+details' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
{
"region": "Europe",
"type": "Summer",
"opening_ceremony": "27 July 2012",
"closing_ceremony": "12 August 2012"
}
curl --location --request POST 'https://zylalabs.com/api/10229/olympic+cities+information+extractor+api/19688/get+olympic+games+info+by+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required","year":"Required"}'
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 Olympic Cities Information Extractor API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The Olympic Cities Information Extractor API specializes in delivering comprehensive data regarding the cities that have hosted the Olympic Games throughout history. It encompasses both Summer and Winter Olympic events, detailing the host cities, the years they hosted, and the type of Olympic Games. The API processes data fields such as 'city_name', 'country', 'year', and 'games_type', structured in a JSON format for easy integration. Domain-specific terminology includes 'Summer Olympics' and 'Winter Olympics', which refer to the two main categories of the Olympic Games. The API adheres to standards for geographical data representation and event categorization. Technical requirements include the ability to handle requests for specific host cities or years, and constraints may involve rate limits on API calls. The output format is JSON, with a schema that includes arrays of objects for each host city, ensuring structured and accessible data retrieval for developers and researchers interested in Olympic history.
The API provides data on both Summer and Winter Olympic Games, including details about the host cities, the years they hosted, and the type of Olympic Games.
The API's output includes data fields such as 'city_name', 'country', 'year', and 'games_type', structured in a JSON format for easy access.
Developers can integrate this API to retrieve historical data about Olympic host cities, allowing them to create applications that showcase Olympic history, analyze trends, or provide educational content.
The API returns data in JSON format, structured with arrays of objects for each host city, ensuring organized and accessible data retrieval.
Yes, the API is designed to process requests for specific host cities or years, enabling users to filter and retrieve targeted information about the Olympic Games.
This endpoint returns a list of cities that have hosted the Olympic Games, including both Summer and Winter events. The response is structured as an array of city names, providing a comprehensive overview of all host cities throughout Olympic history.
The response includes key fields such as 'country', 'city', and 'year', detailing the specific Olympic events hosted in each city. This allows users to access historical data about Olympic locations and their respective hosting years.
Users can customize their requests by providing specific parameters such as 'year' and 'country'. This allows them to retrieve tailored information about the Olympic Games that occurred in that year, including host cities and game types.
The response is organized as an array of objects, each containing fields like 'region', 'type', 'opening_ceremony', and 'closing_ceremony'. This structured format makes it easy for users to extract relevant details about the Olympic events for the specified year.
This endpoint provides detailed information about each host city, including the country, city name, and the years in which the Olympic Games were held there. It allows users to explore the historical significance of each location.
Typical use cases include developing educational tools about Olympic history, creating data visualizations of Olympic trends, and conducting research on the impact of hosting the Games on cities. The API serves as a valuable resource for historians and sports analysts.
Users can leverage the structured JSON data to create dynamic applications, perform data analysis, or generate reports. For instance, they can visualize trends in Olympic hosting or compare the frequency of Summer vs. Winter Games across different regions.
The API sources its data from reputable historical records and databases related to the Olympic Games. Regular updates and validations ensure that the information remains accurate and reliable for users seeking insights into Olympic history.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund