Unofficial Tapology MMA API
Contents#
1.
What is Unofficial Tapology MMA API
1.1. Why Unofficial Tapology MMA API
1. What is Unofficial Tapology MMA API#
This API provides comprehensive information about MMA fighters worldwide, including their personal details and statistics. Real-time data provided by Tapology.1.1 Why Unofficial Tapology MMA API#
Unofficial Tapology MMA API allows you to retrieve detailed information about fighters. It's perfect for applications, websites, or services that need up-to-date fighter data.Base URL:#
https://unofficial-tapology-api.p.rapidapi.com
Authentication#
This API uses two types of authentication depending on how you're accessing it.The x-rapidapi-proxy-secret
header is required and is automatically handled by the platform.
The x-rapidapi-key
header is not required when accessing through RapidAPI.
The x-rapidapi-key
header is required for all requests.
This key is provided to you when you subscribe to the API through the platform.
2. Endpoint#
Get Fighter Details#
Retrieve detailed information about a specific fighter.Endpoint:#
GET /fighter/{fighter_id}
fighter_id
(required): The unique identifier of the fighter. Example: 14607-conor-mcgregor
fields
(optional): Comma-separated list of fields to include in the response. If not specified, all fields are returned.
Available fields:
firstname, lastname, nickname, full_record, losses, draws, no_contest, weight_class, born, current_streak, tko_ko, submission, decision, disqualification
Example Request with fields parameterGET https://unofficial-tapology-api.p.rapidapi.com/fighter/14607-conor-mcgregor?fields=firstname,lastname,full_record,tko_ko
{
"firstname": "Conor",
"lastname": "McGregor",
"full_record": "22-6-0",
"tko_ko": {
"wins": 19,
"losses": 2
}
}
Example Request with all the available objectsGET https://unofficial-tapology-api.p.rapidapi.com/fighter/georges-st-pierre-rush
{
"firstname": "Georges",
"lastname": "St-Pierre",
"nickname": "Rush",
"full_record": "26-2-0",
"wins": 26,
"losses": 2,
"draws": 0,
"no_contest": 0,
"weight_class": "Middleweight",
"born": "St. Isidore, Quebec, Canada",
"current_streak": "13 Wins",
"tko_ko": {
"wins": 8,
"losses": 1
},
"submission": {
"wins": 6,
"losses": 1
},
"decision": {
"wins": 12,
"losses": 0
},
"disqualification": {
"wins": 0,
"losses": 0
}
}
Response Fields#
ā
firstname: Fighter's first name
ā
lastname: Fighter's last name
ā
nickname: Fighter's nickname (if any)
ā
full_record: Complete fight record (wins-losses-draws, NC)
ā
wins: Total number of wins
ā
losses: Total number of losses
ā
draws: Total number of draws
ā
no_contest: Number of no contests
ā
weight_class: Fighter's weight class
ā
born: Fighter's place of birth
ā
current_streak: Current winning/losing streak
ā
tko_ko: TKO/KO statistics (wins and losses)
ā
submission: Submission statistics (wins and losses)
ā
decision: Decision statistics (wins and losses)
ā
disqualification: Disqualification statistics (wins and losses)
Error Codes#
ā 400 Bad Request: Invalid request parameters
š 401 Unauthorized: Missing or invalid API key
ā 404 Not Found: Fighter not found
ā° 429 Too Many Requests: Rate limit exceeded
š» 500 Internal Server Error: Server-side error
Plans and Usage Limits#
Plan | Price | Rate Limit | Monthly Quota | Use Case |
---|
BASIC | Free | 2 requests/min | 750 requests | Ideal for hobbyists or developers testing the API, allowing experimentation without cost. |
PRO | $25/month | 4 requests/min | 3,000 requests | Suitable for freelance developers or small projects requiring more frequent API calls. |
ULTRA | $75/month | 12 requests/min | 9,000 requests | Great for professional developers working on larger projects or small businesses integrating the API into their products. |
MEGA | $150/month | 60 requests/min | 30,000 requests | Designed for high-traffic applications or businesses heavily relying on the API for core functionalities. |
Our per-minute rate limits ensure smooth and responsive API performance while allowing for efficient data retrieval. These limits, combined with the monthly quota, are designed to meet a wide range of usage patterns from occasional testing to high-volume integrations.Best Practices#
1.
Use the fields parameter to request only the data you need, improving response times and reducing data transfer.
2.
Implement caching on your end to store frequently accessed fighter data.
3.
Handle rate limiting by implementing exponential backoff in your requests.
4.
Respect the source data by implementing proper attribution and adhering to fair use principles.
5.
Regularly update cached data to ensure accuracy and freshness of information.
Support#
Changelog#
v1.0.0 (22-07-2024): Initial release of the Unofficial Tapology MMA API
3. Data Source and Fair Use#
The data provided by this API is sourced from Tapology.com. We respect the intellectual property rights of Tapology and adhere to fair use principles. Users and Developers of this API must also comply with fair use guidelines:1.
Attribution: When displaying data obtained through this API, always provide clear attribution to Tapology.com as the original source. 2.
Limited Use: Use the data for informational purposes only. Do not use it in a way that could be considered a replacement for Tapology's services.
3.
No Bulk Downloads: Do not attempt to download or cache large portions of the database. Only request the data you need for immediate use.
4.
Respect Rate Limits: Adhere to the rate limits specified in your plan. These limits are in place partly to ensure fair use of Tapology's data.
5.
No Misrepresentation: Do not present the data in a way that could be misleading or out of context.
6.
Freshness: Consider implementing regular updates in your application to ensure the displayed data is current.
Legal Notice#
This API is not officially affiliated with, endorsed, or sponsored by Tapology.com. It is an independent service that accesses publicly available data in compliance with fair use doctrine. Users are responsible for ensuring their use of the data complies with all applicable laws and Tapology.com's terms of service.Modified atĀ 2024-07-22 17:40:21