Inputs

This page explains the common request inputs used across LineupAPI endpoints.

apiKey

Your subscription key used to authenticate requests.

How it’s used: query parameter
?apiKey=YOUR_API_KEY

Important

Replace YOUR_API_KEY with your real key from the dashboard.
Keep your key secret — treat it like a password.

fixtureId

A unique identifier for a match, in UUID format.

Example: f61793bf-59e8-4d1b-81bd-458a1fd138dd

Where to get it:
Call /fixtures and copy the fixtureId you want.

Where you use it:
You reuse the same fixtureId across:

• /predictions/{fixtureId}
• /predictions/metadata/{fixtureId}
• /history/predictions/{fixtureId}

groups (predictions)

groups controls which prediction groups are included in the response.

Example (single group):
?groups=lineups

Example (multiple groups, comma-separated):
?groups=lineups,goals,assists

Special value:
?groups=all returns all available groups.

Cost reminder

Prediction cost scales with the number of unique groups requested.
Request only what you need.

Common mistakes

• Typos (assist vs assists) → the group may be ignored or appear empty
• Using groups=all by default → higher cost and larger CSV
• Expecting group order to matter → it doesn’t

date (history routes)

History endpoints accept a date timestamp to retrieve a past snapshot.

Format: ISO 8601
Example: 2021-10-18T12:00:00Z

How history resolves timestamps:
The API returns the closest snapshot at or before the timestamp you provide.

UTC / “Z” (Zulu time)

In ISO 8601 timestamps, the trailing Z means UTC time (“Zulu time”).
Example: 2025-04-24T16:00:00Z is 16:00 in UTC.