Submit BSL compact action batch compatibility route
POST/api/v1/mm/orders/batch.bin
This endpoint has been deprecated and may be replaced or removed in future versions of the API.
Trading-plane compact byte route under the legacy /api/v1/mm path. New clients should use POST /api/v1/bsl/orders/compact. Compatibility alias; migrate to /api/v1/bsl/orders/compact. It remains mounted through the compatibility period (retirement review no earlier than 2027-03-07). Signed requests must use the actual request path; no redirect is applied.
Request
Responses
- 200
- 409
- 429
- 503
- default
BSL compact batch result
Conflicting state or Idempotency-Key reused with a different request body. Do not retry with the same key and a different body.
Response Headers
Stable request correlation id generated or echoed by the server.
Admission budget exceeded. Honor Retry-After and the X-RateLimit-* headers before retrying.
Response Headers
Stable request correlation id generated or echoed by the server.
Delay in seconds before another admission attempt. Only emitted on responses that have a known retry delay.
Configured action budget for the current rate-limit window.
Remaining actions in the current rate-limit window.
Milliseconds until the current action rate-limit window resets.
Inferred quota values describe fallback signalling, not measured account capacity.
Temporary admission/readiness or queue-capacity failure. Honor Retry-After; reconcile accepted work before retrying.
Response Headers
Stable request correlation id generated or echoed by the server.
Delay in seconds before another admission attempt. Only emitted on responses that have a known retry delay.
Configured action budget for the current rate-limit window.
Remaining actions in the current rate-limit window.
Milliseconds until the current action rate-limit window resets.
Inferred quota values describe fallback signalling, not measured account capacity.
Error response. Prefer the nested ApiErrorResponse via X-SC-Error-Format: envelope-v1; existing unnegotiated handler responses can retain a documented legacy flat shape through the compatibility period.
Response Headers
Stable request correlation id generated or echoed by the server.