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"}'
Encabezado | Descripción |
---|---|
Autorización
|
[Requerido] Debería ser Bearer access_key . Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito. |
Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.
La API de Datos de Luchadores de MMA proporciona estadísticas detalladas sobre luchadores de MMA, incluyendo sus récords de peleas (victorias, derrotas, empates), atributos físicos (edad, altura, peso, alcance), postura de lucha, resultados de peleas, métodos de victoria (KO/TKO, sumisión, decisión) y tiempos promedio de pelea.
Los datos de la API de Datos de Luchadores de MMA están formateados en JSON, con esquemas específicos para perfiles de luchadores y resultados de peleas. Cada perfil de luchador incluye un identificador único, mientras que los resultados de las peleas están vinculados a eventos específicos, detallando el nombre del evento, la fecha y el formato de la pelea.
Los términos clave incluyen 'combates' (el número de peleas), 'movimiento final' (el método por el cual se gana una pelea) y 'división' (la categoría de peso del luchador). Comprender estos términos te ayudará a interpretar los datos de manera más efectiva.
Sí, la API de Datos de Luchadores de MMA incluye información sobre las próximas peleas, lo que te permite rastrear las peleas programadas y sus detalles asociados.
¡Absolutamente! La API está diseñada para una fácil integración en aplicaciones que rastrean estadísticas de MMA y el rendimiento de los luchadores, proporcionando una salida estructurada que los desarrolladores pueden utilizar.
Este endpoint devuelve información detallada sobre un luchador de MMA, incluyendo detalles personales como nombre, edad, altura, peso, alcance y postura de combate, junto con su historial completo de peleas (victorias, derrotas, empates y métodos de victoria).
Este endpoint proporciona una lista de peleas programadas para un luchador específico, incluyendo detalles como el nombre del evento, la fecha, el oponente y el formato de la pelea, permitiendo a los fanáticos y analistas seguir las actividades del luchador.
La respuesta está estructurada como un arreglo de objetos, cada uno conteniendo una categoría (por ejemplo, Peso Pesado), el nombre del campeón y una lista de clasificaciones con los nombres de los luchadores y sus respectivos rangos, facilitando el fácil acceso a la información de clasificaciones.
Los usuarios pueden especificar la categoría de peso en la que están interesados, como Pesado, Semipesado o Gallo, para recuperar al campeón y a los diez mejores luchadores en esa categoría específica.
Los usuarios pueden personalizar las solicitudes pasando valores de clase de peso específicos en el parámetro de categorías, como Pesado o Pluma, para recibir información de clasificación específica para esa clase.
Los casos de uso típicos incluyen el seguimiento de estadísticas de los luchadores para análisis, seguir próximas peleas para la participación de los fanáticos e integrar datos de clasificación en aplicaciones deportivas para actualizaciones en tiempo real sobre el rendimiento de los luchadores.
Los campos clave incluyen "id" (identificador único del luchador), "nombre," "edad," "altura," "peso," "alcance," "postura," y "récord" (que detalla victorias, pérdidas, empates y métodos de victoria), proporcionando una visión completa del luchador.
La precisión de los datos se mantiene a través de actualizaciones regulares y controles de calidad después de eventos importantes, asegurando que las estadísticas y clasificaciones reflejen la información más actual disponible en el panorama de las MMA.
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.
Nivel de Servicio:
100%
Tiempo de Respuesta:
10,735ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
10,735ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2,212ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
13,796ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
10,735ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
10,841ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
9,411ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
11,715ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
10,739ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
5,935ms