Cashout API

Controls cashout feed

Cashout API allows to control which bets are included in the Cashout Feed.

Cashout Feed

As cashout real-time calculation can be very resource-consuming, we need to know which exact bets we should keep there.

Subscribe Endpoint

Allows to subscribe to a potential cashout amount for specific bets.

betIds should contain only ids of the bets (without player id).

Subscription will wear-out after 10 minutes.

In order to keep bets in the subscription, this endpoint should be called periodically to renew the subscription.

Potential cashout values will be sent via the Cashout Feed.

Cashout Feed

Subscribes to provided bets for realtime data

post

Authorizations

Bearer

HTTPRequired

JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"

Body

application/jsontext/jsonapplication/*+json

betIdsstring[] · nullableRequired

Responses

200

OK

No content

401

Unauthorized

403

Forbidden

500

Internal Server Error

post

/api/Cashout/subscribe

HTTPcURLJavaScriptPython

POST /api/Cashout/subscribe HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 19

{
  "betIds": [
    "text"
  ]
}

application/jsontext/jsonapplication/*+json

No content

Unsubscribe Endpoint

Allows to unsibscribe from cashout values for specific bets.

betIds should contain only ids of the bets (without player id).

Should be called when real-time cashout amount for specific bets is not needed anymore (when player leaves the bet history page or moves to another page).

Unsubscribes from provided bets to stop realtime data

post

Authorizations

Bearer

HTTPRequired

JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"

Body

application/jsontext/jsonapplication/*+json

betIdsstring[] · nullableRequired

Responses

200

OK

No content

401

Unauthorized

403

Forbidden

500

Internal Server Error

post

/api/Cashout/unsubscribe

HTTPcURLJavaScriptPython

POST /api/Cashout/unsubscribe HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 19

{
  "betIds": [
    "text"
  ]
}

application/jsontext/jsonapplication/*+json

No content

Cashout Endpoint

Allows to perform cashout of the bet with risk management check.

Odds88 will perform validation of cashout possibility and cashout amount.

Tries to cashout a bet.

post

Authorizations

Bearer

HTTPRequired

JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"

Body

application/jsontext/jsonapplication/*+json

betIdstring · nullableRequired

priceChangeinteger · enumRequired

• 1 - None
• 2 - Any

Possible values:

Responses

200

OK

text/plainapplication/jsontext/json

successbooleanRequired

reasonstring · nullableOptional

401

Unauthorized

403

Forbidden

500

Internal Server Error

post

/api/Cashout

HTTPcURLJavaScriptPython

POST /api/Cashout HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 91

{
  "betId": "text",
  "priceChange": 1,
  "amount": {
    "localAmount": 1,
    "precision": 1,
    "currency": "text"
  }
}

application/jsontext/jsonapplication/*+json

{
  "success": true,
  "reason": "text",
  "payload": {
    "betId": "text",
    "localAmount": 1
  }
}