Skip to main content

Get BSL action receipts

GET 

/api/v1/bsl/receipts

Receipt semantics

Use receipts to turn fast submit acknowledgements into durable order-state truth. A submit can return HTTP 200 while an individual action later appears as rejected in actionResults[], receipts, execution stream, or drop-copy.

Track these fields together in the client journal:

FieldWhy it matters
idempotencyKeyDedupe and replay safety for the submit envelope.
action noncePer-account sequencing and replay diagnostics.
derivedOrderIds[]Child order ids produced by QuoteReplace legs.
receipt status/codeTerminal accepted, queued, applied, rejected, or dropped state.
seq / stream sequenceGap-fill and drop-copy reconciliation.

When a receipt reports a risk reject, log account, market, book, asset, free, locked, required, nonce, and idempotency key. Then fetch a fresh bootstrap before retrying. If the nonce must change, rebuild and re-sign the action payload.

Polling pattern

curl "$SENTICORE_API_BASE_URL/api/v1/bsl/receipts?account=$ENGINE_ACCOUNT&seqs=$SEQ_LIST&waitMs=$WAIT_MS" \
-H "SC-Auth-Version: 2" \
-H "SC-Key: $API_KEY_ID" \
-H "SC-Nonce: $SC_NONCE" \
-H "SC-Timestamp: $SC_TIMESTAMP" \
-H "SC-Passphrase: $API_PASSPHRASE" \
-H "SC-Signature: $SC_SIGNATURE"

SEQ_LIST is the comma-separated seqs[] returned by the submit response. Use a small waitMs such as 250 to reconcile an ack response without adding another busy-poll loop.

Durable receipt read used to reconcile fast BSL acknowledgements with final action state. A submit can return HTTP 200 while an individual action later appears as rejected in receipts, execution stream, or drop-copy.

Request

Responses

BSL receipts