Cancelling orders - 4casters API

Four cancel variants are supported. All of them respond with the same envelope: { requestID, data: [ ...CancelResponsePayload ] }.

Cancel response payload

Every successful cancel returns one or more entries shaped like this. Note the field-name casing flips between request (orderId/gameId, lowercase d) and response (orderID/gameID, uppercase ID).

{
  "success": true,
  "orderID": "67f45377c18c6697c172afa4",
  "odds": -110,
  "filled": 0,
  "offered": 100,
  "remaining": 100,
  "side": "5c12bc1ce0daba000f47ba8b",
  "number": -3.5,
  "gameID": "688c0516fbc14da0c202d426",
  "userReference": "client-ref-001",
  "description": "Dallas Mavericks +3.5"
}

boolean

true when the order was cancelled.

string

ID of the cancelled order.

number

Amount that was already filled before the cancel landed.

number

Always 0 after a cancel — the offered side is wound down to zero.

number

Amount that was unmatched at cancel time.

number

Odds of the cancelled order in American format, from the maker’s perspective.

string

Participant ID (moneyline/spread) or over/under (totals).

number

Spread or total number; null for moneylines.

string

Game the cancelled order was on.

string

The userReference you set when placing the order, if any.

string

Human-readable description of the bet (e.g. "Dallas Mavericks +3.5").

Cancel by ID

Cancel a single order by its order ID.

Request

[
  "cancelById",
  {
    "requestID": "YOUR_REQUEST_ID",
    "orderId": "ORDER_ID_TO_CANCEL"
  }
]

Response

{
  "requestID": "YOUR_REQUEST_ID",
  "data": [
    {
      "success": true,
      "orderID": "67f45377c18c6697c172afa4",
      "odds": -110,
      "filled": 0,
      "offered": 0,
      "remaining": 100,
      "side": "5c12bc1ce0daba000f47ba8b",
      "number": -3.5,
      "gameID": "688c0516fbc14da0c202d426",
      "userReference": "client-ref-001",
      "description": "Dallas Mavericks +3.5"
    }
  ]
}

Cancel multiple

Cancel a specific set of orders by ID.

Request

[
  "cancelMultiple",
  {
    "requestID": "YOUR_REQUEST_ID",
    "orderIDs": [
      "ORDER_ID_1",
      "ORDER_ID_2",
      "ORDER_ID_3"
    ]
  }
]

Response

data contains one entry per order ID; check each success flag.

{
  "requestID": "YOUR_REQUEST_ID",
  "data": [
    {
      "success": true,
      "orderID": "ORDER_ID_1",
      "odds": -110,
      "filled": 0,
      "offered": 0,
      "remaining": 100,
      "side": "5c12bc1ce0daba000f47ba8b",
      "number": -3.5,
      "gameID": "688c0516fbc14da0c202d426",
      "userReference": "",
      "description": "Dallas Mavericks +3.5"
    },
    {
      "success": false,
      "orderID": "ORDER_ID_2",
      "description": "order already cancelled"
    }
  ]
}

Cancel all by game

Cancel every open order you have on a single game. Optionally narrow the cancel to a specific market by passing type, side, and/or market.

Request

[
  "cancelAllByGame",
  {
    "requestID": "YOUR_REQUEST_ID",
    "gameId": "GAME_ID_TO_CANCEL",
    "type": "spread",
    "side": "5c12bc1ce0daba000f47ba8b",
    "market": "main"
  }
]

string

required

Game whose orders should be cancelled.

string

Optional — filter to a single market type: moneyline, spread, total, or moneyline1x2.

string

Optional — participant ID (moneyline/spread) or over/under (totals).

string

Optional — market identifier (e.g. main).

Response

{
  "requestID": "YOUR_REQUEST_ID",
  "data": [
    {
      "success": true,
      "orderID": "67f45377c18c6697c172afa4",
      "odds": -110,
      "filled": 0,
      "offered": 0,
      "remaining": 100,
      "side": "5c12bc1ce0daba000f47ba8b",
      "number": -3.5,
      "gameID": "688c0516fbc14da0c202d426",
      "userReference": "",
      "description": "Dallas Mavericks +3.5"
    }
  ]
}

Cancel all

Cancel every open order on the account.

Request

[
  "cancelAll",
  {
    "requestID": "YOUR_REQUEST_ID"
  }
]

Response

{
  "requestID": "YOUR_REQUEST_ID",
  "data": [
    {
      "success": true,
      "orderID": "67f45377c18c6697c172afa4",
      "odds": -110,
      "filled": 0,
      "offered": 0,
      "remaining": 100,
      "side": "5c12bc1ce0daba000f47ba8b",
      "number": -3.5,
      "gameID": "688c0516fbc14da0c202d426",
      "userReference": "",
      "description": "Dallas Mavericks +3.5"
    }
  ]
}

Errors

When a cancel cannot be processed, the server responds with the standard error envelope (no data field):

{
  "requestID": "YOUR_REQUEST_ID",
  "error": "order not found"
}

Common error values:

Error	When
`invalid order ID format`	`cancelById` `orderId` is not a valid ObjectID.
`order not found`	The order ID does not exist.
`unauthorized: order does not belong to user`	You’re trying to cancel another user’s order.
`order already cancelled`	The order was already cancelled.
`order is expired`	The order expired before the cancel landed.
`order already graded`	The order has already been graded (settled).
`game not found`	The referenced game is not in the cache.
`Failed to process cancelMultiple`	An unexpected error processing a `cancelMultiple` batch.
`Failed to process cancelAll`	An unexpected error processing `cancelAll`.
`Failed to process cancelAllByGame`	An unexpected error processing `cancelAllByGame`.

For batch cancels (cancelMultiple, cancelAllByGame, cancelAll) per-order failures appear in data with success: false and a description explaining the reason — only an envelope-level error indicates the whole request failed.

​Cancel response payload

​Cancel by ID

​Request

​Response

​Cancel multiple

​Request

​Response

​Cancel all by game

​Request

​Response

​Cancel all

​Request

​Response

​Errors

Cancel response payload

Cancel by ID

Request

Response

Cancel multiple

Request

Response

Cancel all by game

Request

Response

Cancel all

Request

Response

Errors