Titan007 APIlive.titan007.com ↗
Access football match analysis from titan007.com: head-to-head history, recent form, injuries, standings, and team schedules via 2 structured endpoints.
What is the Titan007 API?
The Titan007 Football Match Analysis API provides structured football data across 2 endpoints, covering match previews and team schedules sourced from live.titan007.com. The get_match_analysis endpoint returns head-to-head history, injury reports, league standings, and recent form for both teams in a single call. The get_team_schedule endpoint delivers a full season calendar with past results and upcoming fixtures for any team by numeric ID.
curl -X GET 'https://api.parse.bot/scraper/98cde336-83bf-4dad-b47c-fe337266e35b/get_match_analysis?match_id=2925514' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace live-titan007-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Titan007 Football Analysis API — match analysis and team schedules."""
from parse_apis.live_titan007_com_api import Titan007, MatchNotFound
client = Titan007()
# Fetch a team's schedule for the current year
schedule = client.schedules.get(team_id="47543", year="2026")
print(f"{schedule.total_matches} matches in {schedule.year}")
# Pick the first future fixture from the schedule
future = [f for f in schedule.matches if f.is_future]
if future:
fixture = future[0]
print(f"Next: {fixture.home_team_en} vs {fixture.away_team_en} ({fixture.datetime})")
# Use the fixture's match_id to get full pre-match analysis
try:
analysis = client.match_analyses.get(match_id=str(fixture.match_id))
except MatchNotFound:
print("Analysis not yet available for this fixture")
analysis = None
if analysis:
print(f"League: {analysis.league}, Kickoff: {analysis.match_time}")
print(f"Standings — Home: #{analysis.standings.home.rank}, Away: #{analysis.standings.away.rank}")
# Head-to-head history
for h2h in analysis.head_to_head[:3]:
print(f" {h2h.date}: {h2h.home_team} {h2h.home_score}-{h2h.away_score} {h2h.away_team}")
# Injuries for the home side
for inj in analysis.injuries.home:
print(f" Injury: {inj.player} — {inj.reason}")
print("exercised: schedules.get / match_analyses.get")
Returns comprehensive match analysis for a given match: head-to-head history between the two teams, recent form for both home and away teams, injury/absence reports, and league standings with current rank. Data is extracted from the analysis page. One HTTP round-trip per call. Only matches that have started or are scheduled will have analysis pages.
| Param | Type | Description |
|---|---|---|
| match_idrequired | string | Numeric match identifier from titan007 (e.g. from live scores page or team schedule). The match must exist on the site. |
{
"type": "object",
"fields": {
"league": "string - league name and round",
"injuries": "object with home and away arrays of injured/absent players",
"match_id": "integer - the match identifier",
"away_team": "string - away team name in Chinese",
"home_team": "string - home team name in Chinese",
"standings": "object with home and away league rank info",
"match_time": "string - scheduled kickoff time (YYYY-MM-DD HH:MM)",
"away_recent": "array of away team's recent match results",
"home_recent": "array of home team's recent match results",
"away_team_id": "integer - numeric team ID for the away team",
"head_to_head": "array of past meetings between these two teams",
"home_team_id": "integer - numeric team ID for the home team"
},
"sample": {
"data": {
"league": "韩K2联 第23轮",
"injuries": {
"away": [],
"home": [
{
"player": "66 (左后卫) 郑宇宰",
"reason": "复出"
}
]
},
"match_id": 2925514,
"away_team": "龙仁",
"home_team": "忠南牙山",
"standings": {
"away": {
"rank": 12,
"team": "龙仁",
"league_info": "韩K2联"
},
"home": {
"rank": 8,
"team": "忠南牙山",
"league_info": "韩K2联"
}
},
"match_time": "2026-08-23 18:30",
"away_recent": [
{
"date": "26-08-07",
"handicap": "-0.5",
"match_id": 2925499,
"away_team": "釜山偶像",
"home_team": "龙仁",
"league_id": 1292,
"away_score": 0,
"half_score": "0-0",
"home_score": 2,
"league_name": "韩K2联",
"away_team_id": 501,
"home_team_id": 7798,
"handicap_result": 1
}
],
"home_recent": [
{
"date": "26-08-19",
"handicap": "-0.75",
"match_id": 3049482,
"away_team": "大田韩亚市民",
"home_team": "忠南牙山",
"league_id": 468,
"away_score": 3,
"half_score": "1-1",
"home_score": 2,
"league_name": "韩国杯",
"away_team_id": 488,
"home_team_id": 47543,
"handicap_result": -1
}
],
"away_team_id": 7798,
"head_to_head": [
{
"date": "26-05-24",
"handicap": null,
"match_id": 2925433,
"away_team": "忠南牙山",
"home_team": "龙仁",
"league_id": 1292,
"away_score": 0,
"half_score": "0-0",
"home_score": 0,
"league_name": "韩K2联",
"away_team_id": 47543,
"home_team_id": 7798,
"handicap_result": 0
}
],
"home_team_id": 47543
},
"status": "success"
}
}About the Titan007 API
Match Analysis Data
The get_match_analysis endpoint accepts a match_id string (the numeric identifier used on titan007's live scores pages) and returns a structured object covering the key pre-match context. Response fields include home_team and away_team names in Chinese, match_time in YYYY-MM-DD HH:MM format, league name and round, and match_id as an integer. The injuries object contains separate home and away arrays listing each team's injured or absent players. The standings object surfaces current league rank information for both sides, and home_recent / away_recent arrays capture each team's recent results in sequence.
Team Schedule Data
The get_team_schedule endpoint takes a required team_id and an optional year parameter (four-digit, defaults to the current year). It returns a matches array ordered newest to oldest, with each entry carrying fixture or result details — past matches include scores and handicap results, while future fixtures appear without scores. The response also exposes total_matches as an integer count and echoes back team_id and year for confirmation.
Coverage and Language Notes
Team names are returned in Chinese throughout both endpoints, reflecting titan007's primary audience. Match and team identifiers (e.g. match_id, team_id, away_team_id) are numeric and are sourced from titan007's own match and team pages. No translation layer or identifier mapping to other data providers is included in the current API surface.
The Titan007 API is a managed, monitored endpoint for live.titan007.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when live.titan007.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official live.titan007.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build pre-match preview pages using head-to-head history and recent form from
get_match_analysis. - Track injury and absence lists for both teams before a fixture using the
injuriesresponse field. - Display current league standings context alongside a specific match using the
standingsobject. - Generate a team's full season fixture list including upcoming matches using
get_team_schedule. - Compare handicap results across past fixtures by parsing the
matchesarray fromget_team_schedule. - Power a football betting research tool by correlating recent form, injuries, and standings in one workflow.
- Identify a team's remaining schedule for a given year by filtering
matchesentries with no score.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does titan007.com have an official public developer API?+
What does the `injuries` field in `get_match_analysis` actually contain?+
injuries field is an object with two arrays: home and away. Each array lists the injured or absent players reported for that team ahead of the match. The level of detail per player depends on what titan007 surfaces for that fixture — not all matches will have populated injury lists.Are live scores or in-match statistics available through this API?+
Does `get_team_schedule` cover multiple seasons at once?+
year parameter. To build a multi-year history, you would need to call the endpoint once per year with the same team_id. Fetching multiple years in a single call is not supported. You can fork this API on Parse and revise it to add a multi-year batched schedule endpoint.Are team and match identifiers compatible with other football data sources?+
match_id and team_id values are specific to titan007's own numbering scheme and are not mapped to identifiers used by other football data providers such as Opta, Transfermarkt, or FIFA. You would need to maintain your own cross-reference table if combining this data with other sources.