Endpoint & Required Headers
This Navigation Data for Applications service allows the retrieval of the full Betfair market navigation menu from a compressed file.
Best Practice
The file data is cached and new request for the file once an hour should be suitable for those looking to accurately recreate the Betfair navigation menu.
The following request headers are required:
X-Application - Your Application Key
X-Authentication - Your session token, obtained from the API login response.
Example Request
GET https://api.betfair.com/exchange/betting/rest/v1/en/navigation/menu.json Connection: keep-alive X-Application: <AppKey> X-Authentication: <SessionToken> Accept: application/json Accept-Encoding: gzip,deflate
Supported Locales
The following languages are supported by the navigation file:
en | en_GB | da | de | es | it | pt | ru | sv
English - en
Spanish - es
Italian - it
German - de
Swedish - sv
Portuguese -pt
Russian - ru
Danish - da
Navigation Data File Structure
This is a diagram showing how the Navigation Data File is structured.
In plain English:
A ROOT group node has one or many EVENT_TYPE nodes
An EVENT_TYPE node has zero, one or many GROUP nodes
An EVENT_TYPE node has zero, one or many EVENT nodes
A Horse Racing EVENT_TYPE node has zero, one or many RACE nodes
A RACE node has one or many MARKET nodes
A GROUP node has zero, one or many EVENT nodes
A GROUP node has zero, one or many GROUP nodes
An EVENT node has zero, one or many MARKET nodes
An EVENT node has zero, one or many GROUP nodes
An EVENT node has zero, one or many EVENT nodes
JSON Model Structure
ROOT
|
EVENT_TYPE
|
GROUP
|
EVENT
|
RACE
|
MARKET
|