Filtering & sorting

List endpoints share a consistent filter and sort vocabulary so you can write generic client code once.

Filter operators

For most fields, append an operator with double-underscore syntax:

Operator	Meaning	Example
`eq` (default)	Equal	`?team=LAL`
`ne`	Not equal	`?team__ne=LAL`
`gt` / `gte`	Greater than	`?points__gte=30`
`lt` / `lte`	Less than	`?points__lt=10`
`in`	One of (comma-separated)	`?team__in=LAL,BOS,GSW`
`contains`	Substring (case-insensitive)	`?headline__contains=trade`

Common filters

since=<ISO 8601> — only return items updated since this timestamp
since=1h, since=24h, since=7d — relative shortcuts
league=nba
team=LAL or team__in=LAL,BOS
season=2024-25
date_from=2025-10-22 / date_to=2025-11-14

Sorting

Use order=<field> for ascending, order=-<field> for descending. Each list endpoint documents which fields are sortable.

# Newest news first
GET /v1/news?order=-published_at

# Highest-scoring players first
GET /v1/nba/players?order=-points_per_game

Combining filters

Filters are AND-ed together. Use __in to express OR within a single field. For more complex predicates (OR across fields), see the q= query language on the news search endpoint.