Metadata API Guide
Overview
The Metadata API provides reference data for sports, locations, leagues, periods, and incidents. Use these endpoints to look up IDs and names for filtering and display purposes.
Base URL: https://engage-api.lsports.eu/api/metadata
All endpoints use the same credential-based authentication as the Customers API. Omit optional filter fields (or pass an empty array) to return the full dataset.
Common request fields
packageId
integer
Yes
Your package ID
username
string
Yes
Your username
password
string
Yes
Your password
Common validation errors (400)
"PackageId must be a positive integer""Username is required""Password is required""Invalid package credentials""Package is inactive"
Server error (500)
Endpoints
1. Get Sports
Returns a dictionary of sport IDs and names available in the platform.
Request body
sportIds
integer[]
No
Filter by specific sport IDs. Returns all sports if omitted or empty.
Success (200)
cURL
2. Get Locations
Returns a dictionary of location IDs and names (countries and regions).
Request body
locationIds
integer[]
No
Filter by specific location IDs. Returns all locations if omitted or empty.
Success (200)
cURL
3. Get Leagues
Returns a dictionary of league IDs and names. Leagues can be filtered by sport and/or location.
Request body
sportIds
integer[]
No
Filter by sport IDs.
locationIds
integer[]
No
Filter by location IDs.
Success (200)
cURL
4. Get Periods
Returns periods grouped by sport. Each period has a display ID and a name.
Request body
sportIds
integer[]
No
Filter by sport IDs. Returns periods for all sports if omitted or empty.
Success (200)
The top-level keys are sport IDs. The id field within each period is the display ID used in fixture and incident messages — use this to match periods in your integration.
cURL
5. Get Incidents
Returns a flat dictionary of all incident type IDs and names. No filters are supported — the full list is always returned.
Request body
Success (200)
cURL
Last updated
Was this helpful?