UFC - MMA Live Fighter Data API

API ID 13421

Live fighter records, fight cards, and bout predictions scraped directly from Tapology on every request — not a stale nightly snapshot.

8,831 ms avg response

API Documentation

Endpoints

Request
Scrapes a fighter's profile live. Returns bio, physical stats, record, last-5 form.
Endpoint ID: 29070
GET https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29070/fighter+profile
INPUT PARAMETERS

Fighter Profile — Endpoint Features

Object Description
url Required Tapology url

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

url
API EXAMPLE RESPONSE
JSON
{
    "success": true,
    "name": "Duško Todorović",
    "nickname": "Thunder",
    "weight": "186.0 lbs",
    "height": "6'1\" (185cm)",
    "reach": "74.0\" (188cm)",
    "age": "32",
    "country": "Kotor, Montenegro",
    "record": "13-6-0",
    "affiliation": "N/A",
    "full_fight_record": "WLLLW",
    "current_match": "U",
    "last_won": "WLLLW"
}
Fighter Profile — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29070/fighter+profile?url=https://www.tapology.com/fightcenter/fighters/114625-duko-todorovi' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Scrapes an event's fight card live. Returns event title/venue and the URL of every bout on the card.
Endpoint ID: 29071
GET https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29071/events
INPUT PARAMETERS

Events — Endpoint Features

Object Description
url Required Tapology url

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

url
API EXAMPLE RESPONSE
JSON
{
    "success": true,
    "event_title": "UFC Fight Night: Medic vs. Rodriguez",
    "event_subtitle": "Belgrade, Serbia",
    "venue": "Belgrade Arena",
    "bout_urls": [
        "https://www.tapology.com/fightcenter/bouts/1139707-ufc-fight-night-uros-the-doctor-medic-vs-daniel-d-rod-rodriguez",
        "https://www.tapology.com/fightcenter/bouts/1159432-ufc-fight-night-jan-blachowicz-vs-navajo-stirling",
        "https://www.tapology.com/fightcenter/bouts/1139708-ufc-fight-night-marcin-tybur-tybura-vs-aleksandar-rocket-rakic",
        "https://www.tapology.com/fightcenter/bouts/1136494-ufc-fight-night-dusko-thunder-todorovic-vs-robert-robzilla-valentin",
        "https://www.tapology.com/fightcenter/bouts/1136049-ufc-fight-night-vlasto-el-chapo-cepo-vs-gilbert-the-rgv-bad-boy-urbina",
        "https://www.tapology.com/fightcenter/bouts/1150626-ufc-fight-night-milos-cobra-janicic-vs-noah-gugnon",
        "https://www.tapology.com/fightcenter/bouts/1141659-ufc-fight-night-ludovit-mr-highlight-klein-vs-tofiq-musayev",
        "https://www.tapology.com/fightcenter/bouts/1145152-ufc-fight-night-michael-pqd-oliveira-vs-oban-the-welsh-gangster-elliott",
        "https://www.tapology.com/fightcenter/bouts/1161794-ufc-fight-night-mark-vologdin-vs-borislav-nikolic",
        "https://www.tapology.com/fightcenter/bouts/1142163-ufc-fight-night-bogdan-the-unleashed-grad-vs-dennis-the-great-buzukja",
        "https://www.tapology.com/fightcenter/bouts/1156341-ufc-fight-night-mateusz-rebecki-vs-kyle-killshot-prepolec",
        "https://www.tapology.com/fightcenter/bouts/1143148-ufc-fight-night-nina-queen-beast-nikolija-milosevic-vs-all-hail-hailey-cowan",
        "https://www.tapology.com/fightcenter/bouts/1161273-ufc-fight-night-jovan-leka-vs-alexander-ironside-poppeck",
        "https://www.tapology.com/fightcenter/bouts/1152879-ufc-fight-night-marina-maki-beki-spasic-vs-stephanie-rondinha-luciano"
    ]
}
Events — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29071/events?url=https://www.tapology.com/fightcenter/events/142997-ufc-fight-night' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Scrapes a single bout live. Returns weight class, both fighters, and crowd-prediction percentages.
Endpoint ID: 29072
GET https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29072/bout+data
INPUT PARAMETERS

Bout Data — Endpoint Features

Object Description
url Required Topology URL

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

url
API EXAMPLE RESPONSE
JSON
{
    "success": true,
    "event_class": null,
    "weight_class": null,
    "fight_type": null,
    "fighter1_name": "Uros Medic",
    "fighter1_nickname": "Strength of Schedule",
    "fighter1_url": "https://www.tapology.com/fightcenter/fighters/175629-uros-medic",
    "fighter1_overall": null,
    "fighter1_ko_tko": "96.4%",
    "fighter1_submission": "0.4%",
    "fighter1_decision": "3.1%",
    "fighter2_name": "Daniel Rodriguez",
    "fighter2_nickname": "Strength of Schedule",
    "fighter2_url": "https://www.tapology.com/fightcenter/fighters/61421-daniel-rodriguez",
    "fighter2_overall": null,
    "fighter2_ko_tko": "74.8%",
    "fighter2_submission": "2.4%",
    "fighter2_decision": "22.8%"
}
Bout Data — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29072/bout+data?url=https://www.tapology.com/fightcenter/events/142997-ufc-fight-night' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Scrapes a bout's result live, once Tapology has posted one. Returns winner, method, round/time.
Endpoint ID: 29073
GET https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29073/bout+result
INPUT PARAMETERS

Bout Result — Endpoint Features

Object Description
url Required Topology URL

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

url
API EXAMPLE RESPONSE
JSON
{
    "success": false,
    "winner_name": null,
    "outcome_method": null,
    "outcome_round_time": null
}
Bout Result — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/13421/ufc+-+mma+live+fighter+data+api/29073/bout+result?url=https://www.tapology.com/fightcenter/bouts/1148512-ufc-330-islam-makhachev-vs-the-future-ian-machado-garry' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

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 UFC - MMA Live Fighter Data API simply include your bearer token in the Authorization header.

Headers
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.

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Real-time UFC and MMA data sourced live from Tapology — fighter bios and records, full event fight cards, per-bout matchup predictions (KO/Submission/Decision %), and fight results. Every request scrapes fresh at call time, so records, streaks, and fight-night results are never more than seconds old — unlike cached datasets that go stale the moment a fighter's record changes.

Fighters: name, nickname, weight, height, reach, age, country, pro record, affiliation, last-5 form
Events: title, venue, full fight card with every bout on the night
Bouts: weight class, both fighters, crowd-prediction percentages by method
Results: winner, method, round/time — as soon as Tapology posts them

UFC - MMA Live Fighter Data API FAQs

Each endpoint returns specific live data related to UFC and MMA. The Fighter Profile endpoint provides fighter bios, stats, and records. The Events endpoint returns event details and bout URLs. The Bout Data endpoint offers matchup predictions and fighter statistics, while the Bout Result endpoint delivers the outcome of fights once available.

Key fields include fighter name, nickname, weight, height, reach, age, country, and record for the Fighter Profile. The Events endpoint includes event title, venue, and bout URLs. Bout Data features fighter names, prediction percentages, and weight class, while Bout Result shows the winner, method, and round/time.

The response data is structured in JSON format, with a "success" field indicating the request status. Each endpoint returns relevant data grouped logically, such as fighter details in the Fighter Profile or event information in the Events endpoint, making it easy to parse and utilize.

The Fighter Profile provides detailed fighter statistics and records. The Events endpoint lists upcoming fight cards and venues. The Bout Data endpoint includes matchup predictions and fighter statistics, while the Bout Result endpoint reveals fight outcomes, including the winner and method of victory.

Data accuracy is maintained by scraping live information directly from Tapology with each request. This ensures that the data reflects the most current fighter records, fight results, and event details, minimizing the risk of stale or outdated information.

Typical use cases include developing sports analytics applications, creating real-time fight prediction models, and providing fans with up-to-date fighter profiles and event information. Developers can leverage this data for betting applications, fantasy sports, or enhancing user engagement on sports platforms.

Users can customize their requests by specifying parameters such as fighter names or event titles in the API calls. This allows for targeted data retrieval, enabling users to focus on specific fighters or events of interest, enhancing the relevance of the returned data.

Standard data patterns include consistent JSON structure across endpoints, with fields like "success," "name," and "record" appearing in the Fighter Profile. Users can expect similar organization in event and bout data, facilitating easier integration and analysis of the information provided.

General FAQs

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.

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.

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.

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 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.

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.
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]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund