...
Endpoint | Method | Input URL | Sample Request Body |
|---|---|---|---|
/api/v1/fixtures/{productid}/{eventid} | GET |
| /api/v1/fixtures/4/{131718} |
XML Response Attributes
NAME | DESCRIPTION |
|---|---|
product_id | The ID of the product (In this case ID 5 for Motorsports) |
timestamp | The date & time of when the message was created |
event_id | The ID of the event (Match or Outright) |
expiry_date | The next expiration date of the event (Only for specific Events) |
scheduled_date | The date of when the event will take place |
sport id | The ID of the sport |
sport name | The name of the sport |
category id | The ID of the category |
category name | The name of the category |
tournament id | The ID of the tournament |
tournament name | The name of the tournament |
market name | The name of the market |
outcome id | The ID of the outcome (only for outright) |
outcome name | The name of the outcome (only for outright) |
competitor id | The ID of the competitor (only for match) |
competitor name | The name of the competitor (only for match) |
competitor type | The position of the competitor (this should be used to determine home and away for h2h markets) |
reference id | The mapping id for a particular feed provider/bookmaker |
reference name | The name of the feedprovider/bookmaker mapping id |
reference type | The entity of the feed provider/bookmaker mapping id |
...