The MMA Fighter Data API specializes in handling data related to mixed martial arts fighters, focusing on their performance statistics, personal information, and fight history. It processes various data fields, including fighter names, records (wins, losses, draws), age, height, weight, reach, and fighting stance. The API also tracks fight outcomes, methods of victory (KO/TKO, submission, decision), and average fight times. Domain-specific terminology includes terms like 'bouts', 'finishing move', and 'division', which refer to the number of fights, the method by which a fight is won, and the weight class of the fighter, respectively. The API requires data to be formatted in JSON, with specific schemas for fighter profiles and fight results. Each fighter's profile includes a unique identifier, while fight results are linked to specific events, detailing the event name, date, and fight format. The output is structured to facilitate easy integration into applications that track MMA statistics and fighter performance.
{"id":"Mukhomad Vakhaev","name":"Mukhomad Vakhaev","age":34,"height":"182 cm","weight":"254.6 lbs","reach":"187 cm","stance":"Orthodox","record":{"wins":12,"losses":6,"draws":1}}
curl --location --request POST 'https://zylalabs.com/api/5603/mma+fighter+data+api/7276/get+fighter+profile+by+id' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"fighter":"Required"}'
{"fighter_id":"Mukhomad Vakhaev","bouts":[{"event_name":"ACA 182: Odilov vs. Ibragimov","date":"15.12.2024","opponent":"Anton Vyazigin","format":"3 x 5"}]}
curl --location --request POST 'https://zylalabs.com/api/5603/mma+fighter+data+api/7277/get+upcoming+bouts+for+fighter' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"fighter":"Required"}'
[{"category":"Heavyweight","champion":"Jon Jones","rankings":[{"rank":1,"fighter":"Tom Aspinall"},{"rank":2,"fighter":"Ciryl Gane"},{"rank":3,"fighter":"Alexander Volkov"},{"rank":4,"fighter":"Sergei Pavlovich"},{"rank":5,"fighter":"Curtis Blaydes"},{"rank":6,"fighter":"Jailton Almeida"},{"rank":7,"fighter":"Serghei Spivac"},{"rank":8,"fighter":"Marcin Tybura"},{"rank":9,"fighter":"Jairzinho Rozenstruik"},{"rank":10,"fighter":"Derrick Lewis"},{"rank":11,"fighter":"Tai Tuivasa"},{"rank":12,"fighter":"Marcos Rogerio De Lima"},{"rank":13,"fighter":"Waldo Cortes Acosta"},{"rank":14,"fighter":"Michael Parkin"},{"rank":15,"fighter":"Shamil Gaziev"}]}]
curl --location --request POST 'https://zylalabs.com/api/5603/mma+fighter+data+api/7292/get+current+mma+rankings' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"categories":"Required"}'
[{"category":"Welterweight","champion":"Albert Tumenov","rankings":[{"rank":1,"fighter":"Ustarmagomed Gadzhidaudov"},{"rank":2,"fighter":"Abubakar Vagaev"},{"rank":3,"fighter":"Chersi Dudaev"},{"rank":4,"fighter":"Uzair Abdurakov"},{"rank":5,"fighter":"Anatoliy Boyko"},{"rank":6,"fighter":"Andrey Koshkin"},{"rank":7,"fighter":"Alexey Shurkevich"},{"rank":8,"fighter":"Vinicius Cruz"},{"rank":9,"fighter":"Denis Maher"},{"rank":10,"fighter":"Jakshylyk Myrzabekov"}]}]
curl --location --request POST 'https://zylalabs.com/api/5603/mma+fighter+data+api/7293/get+mma+rankings+aca' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"categories":"Required"}'
[{"rankings":[{"category":"Heavyweight","champion":"Phil De Fries","rank":1,"fighter":"Darko Stosic"},{"category":"Heavyweight","rank":2,"fighter":"Stefan Vojcak"},{"category":"Heavyweight","rank":3,"fighter":"Matheus Scheffel"},{"category":"Heavyweight","rank":4,"fighter":"Szymon Bajor"},{"category":"Heavyweight","rank":5,"fighter":"Michal Mart\u00ednek"},{"category":"Heavyweight","rank":6,"fighter":"Augusto Sakai"},{"category":"Heavyweight","rank":7,"fighter":"Viktor Pesta"},{"category":"Heavyweight","rank":8,"fighter":"Ricardo Prasel"},{"category":"Heavyweight","rank":9,"fighter":"Arkadiusz Wrzosek"},{"category":"Heavyweight","rank":10,"fighter":"Ivan Vitasovi\u0107"}]}]
curl --location --request POST 'https://zylalabs.com/api/5603/mma+fighter+data+api/7294/get+current+ksw+rankings' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"categories":"Required"}'
[{"weight_class":"Women's Flyweight","champion":"Vacant","wrestlers":[{"name":"Aitana Alvarez","rank":1},{"name":"Veronika Smolkova","rank":2},{"name":"Jovana \u0110uki\u0107","rank":3}]}]
curl --location --request POST 'https://zylalabs.com/api/5603/mma+fighter+data+api/7295/get+oktagon+rankings' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"categories":"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 MMA Fighter Data API provides detailed statistics about MMA fighters, including their fight records (wins, losses, draws), physical attributes (age, height, weight, reach), fighting stance, fight outcomes, methods of victory (KO/TKO, submission, decision), and average fight times.
Data from the MMA Fighter Data API is formatted in JSON, with specific schemas for fighter profiles and fight results. Each fighter profile includes a unique identifier, while fight results are linked to specific events, detailing the event name, date, and fight format.
Key terms include 'bouts' (the number of fights), 'finishing move' (the method by which a fight is won), and 'division' (the weight class of the fighter). Understanding these terms will help you interpret the data more effectively.
Yes, the MMA Fighter Data API includes information about upcoming bouts, allowing you to track scheduled fights and their associated details.
Absolutely! The API is designed for easy integration into applications that track MMA statistics and fighter performance, providing structured output that developers can utilize.
This endpoint returns detailed information about an MMA fighter, including personal details like name, age, height, weight, reach, and fighting stance, along with their complete fight record (wins, losses, draws, and methods of victory).
This endpoint provides a list of scheduled fights for a specific fighter, including details such as event name, date, opponent, and fight format, allowing fans and analysts to track fighter activities.
The response is structured as an array of objects, each containing a category (e.g., Heavyweight), champion name, and a list of rankings with fighter names and their respective ranks, facilitating easy access to ranking information.
Users can specify the weight class they are interested in, such as Heavyweight, Light Heavyweight, or Bantamweight, to retrieve the champion and top ten fighters in that specific category.
Users can customize requests by passing specific weight class values in the categories parameter, such as Heavyweight or Featherweight, to receive targeted ranking information for that class.
Typical use cases include tracking fighter statistics for analysis, following upcoming bouts for fan engagement, and integrating ranking data into sports applications for real-time updates on fighter performance.
Key fields include "id" (unique fighter identifier), "name," "age," "height," "weight," "reach," "stance," and "record" (which details wins, losses, draws, and victory methods), providing comprehensive fighter insights.
Data accuracy is maintained through regular updates and quality checks after major events, ensuring that the statistics and rankings reflect the most current information available in the MMA landscape.
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:
2,212ms
Service Level:
100%
Response Time:
10,841ms
Service Level:
100%
Response Time:
9,411ms
Service Level:
100%
Response Time:
9,927ms
Service Level:
100%
Response Time:
10,739ms
Service Level:
100%
Response Time:
4,995ms
Service Level:
100%
Response Time:
1,757ms
Service Level:
100%
Response Time:
3,768ms
Service Level:
100%
Response Time:
1,963ms
Service Level:
99%
Response Time:
653ms