RT Developer

Match Center · Match Intelligence

Fixtures and results as the skeleton — RT derby/tier signals and agent-ready headlines on top. Not a raw scores feed.

6 credits per call · POST /api/v1/match-intelligence

Example response captured 2026-06-09 from live POST /api/v1/match-intelligence (North London derby · fixture 900501).

Match Intelligence reads RT's fixture registry, team registry, and season metadata — then layers derby_kind, competition_tier, and rt_signals.headline. Team names come from RT's registry — no raw third-party fixture titles or external JSON passthrough.

Request body

{
  "team_name": "Tottenham Hotspur",
  "team_id": 6,
  "league_name": "Premier League",
  "mode": "upcoming | recent | all",
  "limit": 10
}

mode=recent — finished matches only (FT/AET/PEN with scores).
mode=upcoming — kickoff ≥ now. Club schedules may be sparse between seasons; use recent for demos.
league_name — post-filter on resolved season names; pair with team_name or team_id for reliable results.
Omit team fields to scan global fixtures (still RT-wrapped, not a bulk export).

Response fields

Response field	Provided by	Notes
matches[].fixture_id	RT fixture registry	Stable fixture ID
matches[].kickoff_utc	RT fixture registry	ISO kickoff time
matches[].status	RT fixture registry	state_code · e.g. NS · FT · AET · PEN
matches[].home / away	RT team registry + scores	name · short_code · score
matches[].competition	RT season metadata	league_name · season · sub_type · stage · round
matches[].rt_signals.derby_kind	RT derbies engine	null when not a tracked derby
matches[].rt_signals.competition_tier	RT competition tier	tier_1–tier_4 · null when unclassified
matches[].rt_signals.headline	RT match intelligence	Natural-language hook for agents
meta.team_id	RT entity resolver	Resolved from team_name or team_id
coverage_note	RT API	Coverage caveat for upcoming vs historical fixtures

Coverage (verified against DB audit)

Club competitions in RT fixture registry (~16K rows): Europe big-5 + UCL/UEL/UECL + friendlies.
World Cup 2026: 48 nations in squad pool · 104 scheduled fixtures · 5 prior tournaments with finished results and historical player stats in DB.
mode=upcoming for WC demos (e.g. Brazil + league_name: World Cup); mode=recent for historical WC finals.
Pre-match DNA duels, predicted XI, post-match ratings — roadmap layers on this skeleton.

Not provided

Row-level raw match feeds or external JSON passthrough.
Standalone intelligence/lineups — folded here + Player Cards match context.
Bulk fixtures/scores export decoupled from RT analysis.

Pairs with Verdict (key-player hot takes) and Best XI (lineup aggregates).

Data & usage policy

RT Developer API returns processed football intelligence — seasonal per-90 metrics, cohort percentiles, DNA similarity, verdicts, and shareable PNG cards. You send player identity and options; RT resolves all stat values server-side.

Underlying match and seasonal statistics are licensed from third-party sports data providers and transformed by RT. Display RT as the data source in your integration; follow your agreement if provider attribution is required.

Authentication

Header: Authorization: Bearer rt_sk_...
Positive API Wallet balance before each call · charged on successful 2xx responses only
Response headers: X-RT-Credits-Charged · X-RT-Wallet-Balance

Create keys at Console → API Keys · Top up at Wallet

Example

curl -X POST https://api.risingtransfers.com/api/v1/match-intelligence \
  -H "Authorization: Bearer rt_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"team_name":"Tottenham Hotspur","mode":"recent","limit":3}'

Top up API Wallet →