Credits & usage

LineupAPI uses a credit system to keep pricing predictable and fair.

Credit cost per request

Cost formula

For /fixtures: cost = 1
For /predictions: cost = 1 × [number of unique groups requested]
Example:

• groups=lineups → cost = 1
• groups=lineups,goals,assists → cost = 3
• groups=all → cost = (all available groups)

For /players: cost = 10
For /predictions/metadata: cost = 10

History cost formula

For /history/fixtures: cost = 10
For /history/predictions: cost = 10 x [number of unique groups]

Important

The History route is intentionally higher-cost because they access archived snapshots.
Maintaining historical data (storage, indexing, and fast retrieval) is significantly more expensive than serving the latest snapshot.
History is best used for backtesting and analysis rather than frequent live refreshes.

Where to see your usage

Experienced users can find these extra headers returned on every successful request:

• x-credits-cost: credit cost of this request
• x-credits-used: credits used since last reset
• x-credits-remaining: credits remaining until next reset

Unsuccessful requests (non-2xx responses) do not consume credits.

When credits reset

Credits for your plan reset at 12:00 AM UTC (00:00 UTC) on the the 1st of each month.
This reset time is UTC-based and does not change with your local timezone or daylight saving time.

What happens when you run out?

When credits are exhausted, the API returns an error response 402 "Insufficient credits".
Check Errors & status codes for exact handling.