Skip to main content

​
Historical list REST success envelope

{
  "success": true,
  "data": {
    "results": [],
    "meta": {
      "hasMore": false,
      "nextCursor": null,
      "appliedTimeRange": {
        "startTime": "2026-03-01T00:00:00.000Z",
        "endTime": "2026-03-31T23:59:59.999Z",
        "allTime": false
      }
    }
  },
  "requestId": "c8e2c6e4-80dd-4ffc-9d66-4e31bf64c6b8"
}
Historical list envelopes are used by events, messages, and valid closed positions.

​
Open positions REST success envelope

Open positions use the same outer envelope, but data.meta only contains:
  • hasMore
  • nextCursor

​
Stats REST success envelope

Stats responses use the same outer envelope and return:
  • subject
  • filtersApplied
  • summary
The applied time bounds for stats reads are returned in data.filtersApplied.appliedTimeRange.

​
REST error envelope

{
  "success": false,
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Unauthorized"
  },
  "requestId": "3d66726f-3fd9-4592-a88d-b1e076eb5f22"
}

​
MCP mapping

  • MCP list tools return structured content with the same results and meta shape as the matching REST reads.
  • MCP stats tools return the same subject, filtersApplied, and summary shape as the matching REST reads.
  • MCP errors are returned through the MCP response model instead of the REST envelope.
  • Preserve the REST requestId when debugging HTTP failures with Centaur support.
Last modified on April 14, 2026