Get a hedge request
Where a request stands, by Mercora’s id from the POST response. A caller that lost the response sends the POST again with the same external_id.
Scope: hedge_requests.
Authorizations
A workspace API key (mk_…), made under Settings → Administration → API.
Path Parameters
Mercora's id for the hedge, from the POST response.
Response
The hedge request.
Mercora's id for the hedge: GET /hedge-requests/{id}.
The caller's own id it was sent with.
processing: being planned · awaiting_approval: planned, waiting for an operator to send, accumulate or dismiss it · accumulated: parked to go out with a later hedge on the same month · merged: folded into another hedge's order · sending: the broker order is going out · awaiting_fill: order sent, waiting for the broker's fill · filled: fill recorded · closed: closed without a recorded fill · dismissed: an operator dismissed it · failed: could not be planned or sent; reason says why
processing, awaiting_approval, accumulated, merged, sending, awaiting_fill, filled, closed, dismissed, failed Why it failed, when state is failed.
The order Mercora planned. Null while processing and when planning failed.
The broker's fill, once recorded.
The executed trade in Mercora's futures ledger, once filled.
Only for a workspace that books hedges in Agiboo; null when the hedge names no Agiboo position.
ISO 8601 timestamp.
The hedge in the Mercora Inbox.