The world's easiest
Copa America API for developers ballers.

30 archived matches from the 2024 tournament, with team names, kickoff times, final scores, and half-by-half linescores where recorded. The 2024 tournament played 32 matches — this is a partial archive, not the full tournament record.

Not yet. This is a results archive today — scores only. Odds, lineups, player stats, and a group-table endpoint are not loaded for this competition.

Not currently — this archive covers the completed 2024 tournament. Coverage of future editions is a roadmap item, not a current claim.

Every endpoint listed here reads from our Postgres archive, not an upstream provider. Hitting them does not consume any upstream provider credits or vendor allowance.

Yes for the match routes: GET /v1/matches and GET /v1/matches/:id are free, 1,000 req/day (2,000 with GitHub connected). Head-to-head, GET /v1/teams/:id/h2h-intelligence, is on the Solo plan.

One tournament: the 2024 Copa América, 21 June – 15 July 2024, all 16 teams (the 10 CONMEBOL sides plus 6 invited CONCACAF guests) — but only 30 of the 32 matches the tournament actually played (missing 2). There is no earlier Copa América edition loaded.

Yes. GET /v1/teams/:id/h2h-intelligence?opponent_id=<team-uuid> returns results between two teams across every competition they have met in — not scoped to Copa América alone, so an Argentina vs Brazil query also pulls in World Cup qualifying meetings between them where loaded.

Not automatically today. This is a closed archive of the completed 2024 tournament. Whether the next Copa América gets added when it happens is undetermined — that is not a confirmed roadmap item, not a promise.

Fixtures, scores, teams, match details, head-to-head history, and available odds are exposed through the connected soccer routes. Richer statistics and event panels render only when this competition has a measured, publishable source; an absent panel is not silently replaced with another league's data. Canonical match and national-team identifiers let a product move from schedule to detail without joining on display names.

Freshness depends on the dataset rather than one page-wide timer. Live scores and player statistics can refresh during matches, while fixtures, rosters, absences, and settled historical rows use slower cadences. Read the source date and response metadata before deciding how often your application should poll.

Create an account and API key, then send it as a Bearer token. Start with /v1/matches?sport=football&league=Copa America or /v1/standings?sport=football&league=Copa America so a healthy response is useful even when no match is live. Keep the returned canonical IDs for the detail calls that follow.

Discover identifiers from list responses instead of guessing them from names. Copa America match rows provide the national-team or match identity needed by detail routes. Preserve those IDs in your own records because accents, abbreviations, transfers, and reused display names make name joins unsafe.

The exact season range depends on the dataset and your plan. Use the coverage response and season labels returned by each route before promising a date range to users. Founder plans expose current-season evaluation on Free, up to five seasons on Solo and Trio, and all available history on Edge and Pro.

Copa America is organized by edition or competition cycle rather than a permanent domestic table. Retain the served edition and match status instead of manufacturing a domestic-style season from the kickoff year. Read match status to distinguish scheduled, live, finished, postponed, suspended, or cancelled fixtures. A table or archive and a future fixture window can legitimately carry different source timestamps.

This page does not claim a dedicated Copa America expected-goals leaderboard today. Match or player statistics appear only when the competition-specific source provides them and the publication checks pass. Treat an absent panel or missing field as unavailable, never as a measured zero or as permission to substitute another competition.

Soccer match events include goals, cards, substitutions, and event timing at scale. They are the soccer equivalent of play-by-play and belong to the Pro capability tier. Use the canonical match ID from the schedule or match list to request the event timeline.

An empty list can be a healthy response for a valid Copa America filter with no matching rows. A null field means the value was unavailable or redacted, and it should not be converted into zero. Check status, pagination, metadata, and the requested season before diagnosing a data gap.

A dedicated Copa America absence feed is not promised on this page today. Do not borrow an injury row from a domestic league or infer availability from a missing lineup. When competition-specific absences are added, they must carry their own source date and preserve the supplied injury, suspension, or other reason.

Your plan and response headers define the enforceable request limits. Poll live Copa America matches more frequently than schedules, rosters, or completed historical statistics. Back off on a 429 response instead of retrying at the same cadence.

Source corrections can change a completed match or player row after the final whistle. Keep canonical IDs so an updated value replaces the same record rather than creating a duplicate. Use the latest source date exposed by the response when auditability matters.

Commercial use depends on your plan and the applicable terms for the fields you use. API access does not itself grant redistribution, sublicensing, trademark, or media rights. Review the terms before shipping a public or customer-facing integration.

Match kickoff records use UTC timestamps. Convert them for display at the edge of your application while retaining the original value for sorting and comparisons. Keep the served tournament edition alongside the timestamp because national-team cycles do not map cleanly to a domestic season.

Read the returned match status rather than inferring state from a blank score or an old kickoff time. Preserve status values your application does not yet recognize so future vocabulary changes do not become false finals. Wait for a terminal status before triggering irreversible settlement or notification logic.