The FC Barcelona Data API specializes in delivering detailed information about FC Barcelona, a prominent football club in La Liga. It processes various data fields such as match fixtures, player statistics (including goals, assists, and minutes played), and historical records.
{"name":"FC Barcelona","founded":"1899","address":"Avenida de Ar\u00edstides Maillol","country":"Spain","city":"Barcelona","stadium":"Estadi Ol\u00edmpic Llu\u00eds Companys","capacity":55926,"phone":"+34 (902) 189 900","fax":"+34 (93) 411 2219","email":"[email protected]"}
curl --location --request POST 'https://zylalabs.com/api/6132/fc+barcelona+data+api/8413/get+fc+barcelona+info' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"attackers":["Ferran Torres","R. Lewandowski","Ansu Fati","Raphinha","Pau V\u00edctor","Lamine Yamal","Toni Fern\u00e1ndez"]}
curl --location --request POST 'https://zylalabs.com/api/6132/fc+barcelona+data+api/8414/get+fc+barcelona+squad' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"position":"Required"}'
{"Name":"R. Lewandowski","Age":36,"Position":"A","Matches":1755,"Goals":22,"Assists":21,"Yellow Cards":1,"Red Cards":11,"Total Shots":2,"Shots on Target":19,"Passes":2,"Passes Completed":1,"Fouls":0,"Offsides":0}
curl --location --request POST 'https://zylalabs.com/api/6132/fc+barcelona+data+api/8415/get+fc+barcelona+player+statistics' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"player":"Required"}'
{"next_matches":[{"date":"17\/02\/25","competition":"LAL","home_team":"Barcelona","away_team":"Rayo Vallecano","time":"21:00"},{"date":"22\/02\/25","competition":"LAL","home_team":"Las Palmas","away_team":"Barcelona","time":"21:00"},{"date":"02\/03\/25","competition":"LAL","home_team":"Barcelona","away_team":"Real Sociedad","time":"-"},{"date":"09\/03\/25","competition":"LAL","home_team":"Barcelona","away_team":"Osasuna","time":"-"},{"date":"16\/03\/25","competition":"LAL","home_team":"Atletico Madrid","away_team":"Barcelona","time":"-"},{"date":"30\/03\/25","competition":"LAL","home_team":"Barcelona","away_team":"Girona","time":"-"},{"date":"06\/04\/25","competition":"LAL","home_team":"Barcelona","away_team":"Real Betis","time":"-"},{"date":"13\/04\/25","competition":"LAL","home_team":"Leganes","away_team":"Barcelona","time":"-"},{"date":"20\/04\/25","competition":"LAL","home_team":"Barcelona","away_team":"Celta Vigo","time":"-"},{"date":"23\/04\/25","competition":"LAL","home_team":"Barcelona","away_team":"Mallorca","time":"-"},{"date":"04\/05\/25","competition":"LAL","home_team":"Real Valladolid","away_team":"Barcelona","time":"-"},{"date":"11\/05\/25","competition":"LAL","home_team":"Barcelona","away_team":"Real Madrid","time":"-"},{"date":"14\/05\/25","competition":"LAL","home_team":"Espanyol","away_team":"Barcelona","time":"-"},{"date":"18\/05\/25","competition":"LAL","home_team":"Barcelona","away_team":"Villarreal","time":"-"},{"date":"25\/05\/25","competition":"LAL","home_team":"Athletic Bilbao","away_team":"Barcelona","time":"-"}]}
curl --location --request POST 'https://zylalabs.com/api/6132/fc+barcelona+data+api/8416/get+fixture+for+fc+barcelona' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"competition":"Required"}'
{"La Liga":{"Winner":{"count":27,"years":["2022\/2023","2018\/2019","2017\/2018","2015\/2016","2014\/2015","2012\/2013","2010\/2011","2009\/2010","2008\/2009","2005\/2006","2004\/2005","1998\/1999","1997\/1998","1993\/1994","1992\/1993","1991\/1992","1990\/1991","1984\/1985","1973\/1974","1959\/1960","1958\/1959","1952\/1953","1951\/1952","1948\/1949","1947\/1948","1944\/1945","1929"]},"Runner-up":{"count":28,"years":["2023\/2024","2021\/2022","2019\/2020","2016\/2017","2013\/2014","2011\/2012","2006\/2007","2003\/2004","1999\/2000","1996\/1997","1988\/1989","1986\/1987","1985\/1986","1981\/1982","1977\/1978","1976\/1977","1975\/1976","1972\/1973","1970\/1971","1967\/1968","1966\/1967","1963\/1964","1961\/1962","1955\/1956","1954\/1955","1953\/1954","1945\/1946","1929\/1930"]}}}
curl --location --request POST 'https://zylalabs.com/api/6132/fc+barcelona+data+api/8417/get+fc+barcelona+trophies' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"competition":"Required"}'
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 retrieve player statistics, you can use the specific endpoint designed for player data, which allows you to query information such as individual player goals, assists, and total minutes played during a season.
Yes, the API includes historical performance metrics, allowing users to access past match results, player performances, and other relevant historical data related to FC Barcelona.
The FC Barcelona Data API primarily focuses on comprehensive data and historical records, and while it includes match fixtures, it may not provide real-time updates during live matches.
The FC Barcelona Data API provides access to comprehensive data including match fixtures, player statistics such as goals, assists, and minutes played, as well as historical performance metrics related to FC Barcelona.
Each endpoint returns specific data types: the FC Barcelona info endpoint provides club details, the squad endpoint lists players by position, the player statistics endpoint offers individual player metrics, the fixture endpoint shows upcoming match schedules, and the trophies endpoint details historical achievements in various competitions.
Key fields include club details like name and founded year from the info endpoint, player names and positions from the squad endpoint, individual stats such as goals and assists from the player statistics endpoint, match dates and competitions from the fixture endpoint, and trophy counts and years from the trophies endpoint.
Parameters vary by endpoint: the squad endpoint requires a position (goalkeeper, defender, midfielder, attacker), the player statistics endpoint needs a specific player name, the fixture endpoint requires a competition name, and the trophies endpoint also needs a competition name to filter results.
Response data is structured in JSON format, with clear key-value pairs. For example, the squad endpoint returns an array of player names categorized by position, while the trophies endpoint organizes data into nested objects for winners and runners-up, detailing counts and years.
Typical use cases include building sports analytics applications, creating fan engagement platforms, developing historical databases for research, and providing real-time updates for sports news websites, all leveraging the detailed data on players, matches, and club achievements.
Users can customize requests by specifying parameters relevant to each endpoint. For instance, when retrieving player statistics, users can select a specific player, and when fetching fixtures, they can choose a particular competition to narrow down the results.
The data is sourced from official FC Barcelona records, match reports, and historical databases, ensuring accuracy and reliability. The API aggregates this information to provide comprehensive insights into the club's performance and statistics.
Users can utilize the returned data by integrating it into applications for displaying player stats, match schedules, or historical records. For example, developers can create dashboards that visualize player performance trends or upcoming fixtures, enhancing user engagement with FC Barcelona content.
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:
5,411ms
Service Level:
100%
Response Time:
469ms
Service Level:
100%
Response Time:
768ms
Service Level:
100%
Response Time:
4,909ms
Service Level:
100%
Response Time:
7,855ms
Service Level:
100%
Response Time:
4,692ms
Service Level:
100%
Response Time:
5,485ms
Service Level:
100%
Response Time:
385ms
Service Level:
100%
Response Time:
7,777ms
Service Level:
100%
Response Time:
7,855ms
Service Level:
100%
Response Time:
2,518ms
Service Level:
100%
Response Time:
143ms
Service Level:
100%
Response Time:
182ms
Service Level:
100%
Response Time:
244ms
Service Level:
100%
Response Time:
87ms
Service Level:
100%
Response Time:
164ms
Service Level:
100%
Response Time:
296ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
86ms
Service Level:
100%
Response Time:
482ms