SofaScore team fixtures API

Endpoint facts

Method

GET

API path

/sofascore/team-events

Auth

apiKey

Credits

0 credits/request

Platform

SofaScore

Response schema

#/definitions/sofascore.teamEventsResponseDoc

Overview

Returns a page of a team's upcoming or recent fixtures from SofaScore's credential-free public JSON. The `direction` enum accepts `next` and `last`. An empty `events` list is a valid response when there is no fixture on that page. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

0 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- An empty `events` array is a valid response when there is no fixture on that page (not an error). - `has_next_page` indicates whether a further page (`page + 1`) has more fixtures in the requested direction. Example response: ```json { "code": 200, "msg": "OK", "data": { "team_id": 2817, "direction": "next", "page": 0, "has_next_page": true, "count": 1, "source_url": "https://api.sofascore.com/api/v1/team/2817/events/next/0", "fetched_at": "2026-07-08T16:45:00Z", "events": [ { "id": 16500000, "slug": "barcelona-real-madrid", "start_timestamp": 1757520000, "start_time": "2026-09-10T19:00:00Z", "status": { "code": 0, "description": "Not started", "type": "notstarted" }, "tournament": { "id": 52, "name": "LaLiga", "category": "Spain", "unique_tournament_id": 8, "unique_tournament_name": "LaLiga" }, "home_team": { "id": 2817, "name": "FC Barcelona", "short_name": "Barcelona", "slug": "barcelona", "country": "Spain" }, "away_team": { "id": 2829, "name": "Real Madrid", "short_name": "Real Madrid", "slug": "real-madrid", "country": "Spain" } } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related