Search fixtures by time window and value filters

get

https://api.sstrader.com/v1/fixtures/search

A powerful query endpoint for discovering fixtures that match specific metric or statistic thresholds. Unlike /fixtures, which retrieves fixtures by date or ID, /search filters by calculated values — for example, find all upcoming matches where the home team's classification metric falls within a given range.
All where[X] filters must match simultaneously (AND logic). Results are paginated and the fixture structure is identical to /fixtures.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Query Params

window

string

enum

Defaults to 24

Defines the time scope of the search.

live — No date range applied; only the status filter drives results. Defaults to all in-play statuses. - 3–168 — Matches fixtures from now up to +N hours from now. Defaults to live + NOT_STARTED statuses.

Allowed:

league_id

string

Comma-separated list of league IDs to restrict the search scope.

status

array of strings

Comma-separated list of fixture statuses to include.
When omitted: window=live defaults to all in-play statuses; numeric windows default to in-play + NOT_STARTED.
Neither default includes DELETED — deleted fixtures are only returned when DELETED is named here explicitly.
👉 View State Definitions

status

where[DEVELOPER_NAME]

string

^\d+:\d+(:(HOME|AWAY|LEAGUE))?$

Value-range filter applied to a named metric or statistic. Format: min:max[:location].

min / max — Integer bounds (inclusive). - location — HOME, AWAY, or LEAGUE (default). Determines which team's value is tested.
Replace DEVELOPER_NAME with a developer_name from the /types endpoint. Up to 10 filters may be specified; all must match (AND logic). Duplicate keys with different locations are supported.
Examples: - where[TEAM_GOALS_CLASSIFICATION]=1100:1800:HOME - where[HOME_AWAY_CLASSIFICATION]=1:2

order[DEVELOPER_NAME]

string

^(ASC|DESC)(:(HOME|AWAY|LEAGUE))?$

Sort results by a named metric or statistic value. Format: DIR[:location].

DIR — ASC or DESC. - location — HOME, AWAY, or LEAGUE (default).
Replace DEVELOPER_NAME with a developer_name from the /types endpoint. Only the first order[...] parameter is applied. Falls back to date_time ASC when no matching value exists for a fixture.
Example: order[TEAM_GOALS_CLASSIFICATION]=DESC:HOME

include

array of strings

Comma-separated list of modules to attach to each fixture. Allowed values: odds, metrics, statistics, metadata, integration. Note: fair_odds and movement are not available on this endpoint. Using an include unlocks the corresponding filter[entity] parameter.

include

Allowed:

filter[integration]

string

^[a-z_]+:[^;]+(;[a-z_]+:[^;]+)*$

Selects which integration answers, and filters by your platform's own ids.
Segments are separated by ;, values inside a segment by ,.

providers:<name> picks the integration. Only ONE per request: if several are listed, the
first is honoured and the rest ignored. The one that answered is named by provider inside
each fixture's integration object. Omitted, it defaults to the integration your API key is
entitled to. Naming an integration you are not entitled to returns 403; naming one that
does not exist returns 400.

Supported here:

ext_league_ids, ext_master_league_ids, ext_country_ids — one of the three per request.

This endpoint selects fixtures by metric value ranges and has no event or team predicate, so
ext_event_ids, the team keys and mapped_only return 400 here. Use /fixtures.

Send ids exactly as you receive them in the integration object, as strings — they are
64-bit values that a JSON number cannot hold without corruption.

An id we have no mapping for is not an error: you get an empty list, never an unfiltered
one. Coverage grows as we see more of your events.

A key this endpoint does not support returns 400 rather than being ignored, and so does
naming the same thing twice — league_id with a league key, or fixture_id with
ext_event_ids.

filter[metrics]

string

Optional filter for the included metrics module. Use this to specify which metrics to include based on their Type IDs or domain groups.

filter[statistics]

string

Optional filter for the included statistics module. Use types:ID,... to return only specific statistic types.

filter[odds]

string

Refine the odds data by applying specific keys. Use a comma (,) for OR logic within a key and a semicolon (;) for AND logic between different keys.

language

string

Defaults to en

Localization code for team, league, and country names. Alias: lang.

page

integer

≥ 1

Defaults to 1

The current page number.

per_page

integer

1 to 50

Defaults to 25

Results returned per page. Maximum is 50.

Responses

403

Unauthorized — missing or insufficient permissions.

200A list of matching fixtures with pagination metadata.

400Validation error. Possible causes: - Invalid window value. - Malformed where[X] filter (non-numeric or missing min/max). - More than 10 where filters provided.