The Stadiums Data API is designed to extract and serve information about the world's largest football stadiums, based on the dataset available on Wikipedia. The API allows users to query stadium details in a structured way, preventing data overload by dividing requests into separate endpoints. Users can retrieve lists of countries with stadiums, get all stadiums in a specific country, and fetch detailed information about a specific stadium.
{"countries":["North Korea","United States","Australia","Spain","South Africa","Egypt","Malaysia","Mexico","Qatar","Germany","Ireland","Indonesia","China","Brazil","Iran","Russia","Turkey","Japan","Ukraine","Saudi Arabia","Canada","Portugal","Algeria","Senegal","Tanzania","Kuwait","Tunisia","India","Somalia","Zambia","Ecuador","Poland","Ghana","Colombia","Lebanon","South Korea","Vietnam","New Zealand","Angola","DR Congo","Zimbabwe","Mali","Pakistan"]}
curl --location --request POST 'https://zylalabs.com/api/6190/stadiums+data+api/8629/countries+with+stadiums' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[{"stadium_name":"Guangdong Olympic Stadium"},{"stadium_name":"Hangzhou Olympic Sports Expo Centre Stadium"},{"stadium_name":"Beijing National Stadium"},{"stadium_name":"Shanghai Stadium"},{"stadium_name":"Nissan Stadium"},{"stadium_name":"Shenzhen Universiade Sports Centre Stadium"},{"stadium_name":"Shenyang Olympic Sports Centre Stadium"},{"stadium_name":"Harbin Sports City Centre Stadium"},{"stadium_name":"Xinjiang Sports Centre Stadium"},{"stadium_name":"Zibo Sports Centre Stadium"},{"stadium_name":"Weifang Sports Centre Stadium"},{"stadium_name":"Yantai Sports Park Stadium"},{"stadium_name":"Bao'an Stadium"},{"stadium_name":"Kunming Tuodong Sports Centre Stadium"},{"stadium_name":"Wuhu Olympic Stadium"},{"stadium_name":"Huizhou Olympic Stadium"}]
curl --location --request POST 'https://zylalabs.com/api/6190/stadiums+data+api/8630/get+stadiums+by+country' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"country":"Required"}'
{"Stadium":"Nissan Stadium","Seating capacity":"72,327","Region":"East Asia","Country":"Japan","City":"Yokohama, Kanagawa","Home team(s)":"Yokohama F. Marinos, Yokohama Eagles"}
curl --location --request POST 'https://zylalabs.com/api/6190/stadiums+data+api/8631/get+stadium+details' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"stadium":"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 Stadiums Data API allows you to retrieve structured information about association football stadiums worldwide, including details such as stadium capacity, location, and other relevant information.
You can retrieve a list of all stadiums in a specific country by using the designated endpoint that queries stadiums based on the country parameter.
Yes, the API provides an endpoint that allows you to fetch detailed information about a specific stadium by using its unique identifier.
The Stadiums Data API prevents data overload by segmenting the data into specific endpoints, allowing users to make targeted queries rather than retrieving all data at once.
The Stadiums Data API allows you to retrieve structured information about association football stadiums worldwide, including details such as their capacity, location, and specific attributes. You can query lists of countries with stadiums, obtain all stadiums in a specific country, and fetch detailed information about individual stadiums.
The "countries with stadiums" endpoint returns a list of countries. The "get stadiums by country" endpoint returns a list of stadium names within a specified country. The "get stadium details" endpoint provides detailed information about a specific stadium, including its seating capacity, region, country, city, and home teams.
Key fields include "countries" in the first endpoint, "stadium_name" in the second, and "Stadium," "Seating capacity," "Region," "Country," "City," and "Home team(s)" in the third endpoint's response.
Responses are structured in JSON format. The first endpoint returns an array of country names, the second returns an array of stadium objects, and the third returns a single stadium object with detailed attributes.
The "get stadiums by country" endpoint requires a "country" parameter, while the "get stadium details" endpoint requires a "stadium name" parameter. These parameters help customize the data requests to retrieve specific information.
The first endpoint provides a list of countries with stadiums. The second endpoint lists stadiums in a specified country, while the third endpoint offers detailed information about a specific stadium, including its capacity and location.
Users can utilize the data to analyze stadium distribution by country, compare stadium capacities, or gather detailed information for specific venues. For example, retrieving stadium details can aid in planning events or understanding regional football infrastructure.
The Stadiums Data API sources its data from publicly available information, primarily from Wikipedia, ensuring a broad and diverse dataset of football stadiums worldwide.
Typical use cases include sports analytics, event planning, travel research for football fans, and academic studies on sports infrastructure. Users can leverage the data to gain insights into stadium capacities and locations globally.
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 1,000 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 1,000 requests per month, this header will display 1,000.
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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
10,237ms
Service Level:
100%
Response Time:
5,583ms
Service Level:
100%
Response Time:
3,797ms
Service Level:
100%
Response Time:
3,944ms
Service Level:
100%
Response Time:
3,154ms
Service Level:
100%
Response Time:
577ms
Service Level:
85%
Response Time:
454ms
Service Level:
100%
Response Time:
8,515ms
Service Level:
100%
Response Time:
913ms
Service Level:
100%
Response Time:
512ms
Service Level:
100%
Response Time:
1,810ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
242ms
Service Level:
83%
Response Time:
396ms
Service Level:
100%
Response Time:
331ms
Service Level:
100%
Response Time:
496ms
Service Level:
100%
Response Time:
915ms
Service Level:
100%
Response Time:
693ms
Service Level:
100%
Response Time:
5,800ms
Service Level:
100%
Response Time:
532ms