Bet365 API

Bet365 InPlay

GET/v1/bet365/inplay

The whole bet365 in-play list, as bet365 structures it.

Parameters

Send every parameter in the query string, including token.

Query parameters
Name	Type	Required	Description
token	string	Required	Your API token.
raw	boolean	Optional	Return the capture before parsing.

Notes

There is no FI in this list. Pass ID to Bet365 Inplay Event, or use Bet365 InPlay Filter.

Request

Call https://api.odds-data-api.com/v1/bet365/inplay with your token. The examples read it from the ODDS_DATA_API_TOKEN environment variable.

curl "https://api.odds-data-api.com/v1/bet365/inplay?token=$ODDS_DATA_API_TOKEN"

Response

JSON with success: 1 and results. Values are strings unless shown otherwise. See Response format and R-Pager.

application/json

{
  "success": 1,
  "results": [
    [
      {
        "type": "CL",
        "ID": "1",
        "NA": "Soccer"
      },
      {
        "type": "CT",
        "NA": "England Premier League"
      },
      {
        "type": "EV",
        "ID": "158204771C1A_1_1",
        "NA": "Brentford v Everton",
        "SS": "2-1",
        "TM": "67",
        "TS": "12",
        "TT": "1"
      }
    ]
  ]
}

Errors

A failed call returns success: 0 with an error code. This endpoint can return:

Error codes
error	Meaning
AUTHORIZE_FAILED	Token is not provided or is incorrect.
TOO_MANY_REQUESTS	API rate limit exceeded. See X-RateLimit-Reset.
PERMISSION_DENIED	Your plan does not include this call. Contact support if this is wrong.
PARAM_INVALID	A param is invalid. Check error_detail.

Failed call · application/json

{
  "success": 0,
  "error": "AUTHORIZE_FAILED"
}

Like every endpoint, it can also return INTERNAL_SERVER_ERROR, METHOD_NOT_ALLOWED and UNDER_MAINTENANCE. See R-Errors.

Try it

GEThttps://api.odds-data-api.com/v1/bet365/inplay?token=YOUR-TOKEN

token: YOUR-TOKEN (from the dashboard)

Requests run with your own token and count toward your hourly limit.