Common Parameters - AnySport

Most REST endpoints use one or more of the following three parameters. Their semantics are consistent across all endpoints, so they’re documented here separately, whether a specific endpoint supports them, and whether they’re required, is determined by that endpoint’s own parameter table.

Parameter	Type	Required	Default	Description
`lang`	string	No	en	Language for name-type fields. Currently supports `en` (English); `zh-CN` (Simplified Chinese) is being rolled out progressively
`page`	int	No	1	Page number, starting from 1 (paginated endpoints)
`limit`	int	No	50	Number of items per page, range 1–100 (paginated endpoints)

lang: multi-language names

lang affects the language of name-type fields — such as country names, league names, team names, player names, and other human-readable text; it does not affect the format of structured fields like IDs, dates, or numbers. If lang is not provided, English names are returned by default.

# Returns the English league name
GET /v1/soccer/leagues?league_id=asl_62db...&lang=en

# Returns the Chinese league name (coverage is being expanded progressively)
GET /v1/soccer/leagues?league_id=asl_62db...&lang=zh-CN

Translation coverage for zh-CN is being expanded on an ongoing basis, and translation completeness may vary across entity types (countries/leagues/teams/players). If your use case has strict multi-language display requirements, we recommend implementing a fallback on the frontend to show the English name when a translation isn’t available.

page / limit: pagination

Only endpoints explicitly marked as “paginated” support these two parameters; passing them to a non-paginated endpoint will not cause an error, but they will have no effect.

page starts counting from 1, not 0.
The valid range for limit is 1–100; values outside this range are treated as invalid parameters by the gateway, returning 400 INVALID_PARAMS.
For the total / page / limit / total_pages fields in the response meta, see Response Format for usage details.

If you need to fetch the full dataset of a resource type (e.g. all countries, all leagues), we recommend paginating through it at the limit=100 maximum rather than trying to fetch everything in a single request — this both aligns with the endpoint design and lets your client handle large datasets more smoothly.