Create New Clearing Order
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:create assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlCreate New Clearing Order › Request Body
requestThe literal string "/v1/clearing/new"
The nonce, as described in Private API Invocation
symbolThe trading pair
amountThe amount to trade
priceThe price
sideThe direction of the trade
counterparty_idThe counterparty ID
expires_in_hrsThe number of hours until the order expires
accountRequired for Master API keys. The name of the account within the subaccount group.
Create New Clearing Order › Responses
Successful operation
clearing_idThe clearing ID
symbolThe trading pair
priceThe order price
amountThe order amount
sidestatusThe order status
timestamp
timestampmsThe timestamp in milliseconds
is_confirmedWhether the order is confirmed
Get Clearing Order
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:read assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlGet Clearing Order › Request Body
requestThe literal string "/v1/clearing/status"
The nonce, as described in Private API Invocation
clearing_idThe clearing ID
accountRequired for Master API keys. The name of the account within the subaccount group.
Get Clearing Order › Responses
Successful operation
clearing_idThe clearing ID
symbolThe trading pair
priceThe order price
amountThe order amount
sidestatusThe order status
timestamp
timestampmsThe timestamp in milliseconds
is_confirmedWhether the order is confirmed
Cancel Clearing Order
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:create assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlCancel Clearing Order › Request Body
requestThe literal string "/v1/clearing/cancel"
The nonce, as described in Private API Invocation
clearing_idThe clearing ID
accountRequired for Master API keys. The name of the account within the subaccount group.
Cancel Clearing Order › Responses
Successful operation
resultStatus of the cancel operation
detailsDetailed description of the result
Confirm Clearing Order
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:create assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlConfirm Clearing Order › Request Body
requestThe literal string "/v1/clearing/confirm"
The nonce, as described in Private API Invocation
clearing_idThe clearing ID
symbolThe trading pair
amountThe amount to trade
priceThe price
sideThe direction of the trade
accountRequired for Master API keys. The name of the account within the subaccount group.
Confirm Clearing Order › Responses
Successful operation
resultStatus of the confirmation operation
List Clearing Orders
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:read assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlList Clearing Orders › Request Body
requestThe literal string "/v1/clearing/list"
The nonce, as described in Private API Invocation
symbolTrading pair
counterpartycounterparty_id or counterparty_alias
side"buy" or "sell"
UTC timestamp. Requires expiration_end if set
UTC timestamp. Requires expiration_start if set
UTC timestamp. Requires submission_end if set
UTC timestamp. Requires submission_start if set
fundedDefault value false if not set
statusFilter by status
Only return orders after this timestamp
limit_ordersThe maximum number of orders to return
accountRequired for Master API keys. The name of the account within the subaccount group.
List Clearing Orders › Responses
Successful operation
resultStatus of the operation
List Clearing Brokers
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:read assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlList Clearing Brokers › Request Body
requestThe literal string "/v1/clearing/broker/list"
The nonce, as described in Private API Invocation
symbolTrading pair
UTC timestamp. Requires expiration_end if set
UTC timestamp. Requires expiration_start if set
UTC timestamp. Requires submission_end if set
UTC timestamp. Requires submission_start if set
fundedDefault value false if not set
statusFilter by status
Only return orders after this timestamp
limit_ordersThe maximum number of orders to return
accountRequired for Master API keys. The name of the account within the subaccount group.
List Clearing Brokers › Responses
Successful operation
resultStatus of the operation
Create New Broker Order
Gemini Clearing also allows for brokers to facilitate trades between two Gemini customers. A broker can submit a new Gemini Clearing order that must then be confirmed by each counterparty before settlement.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlCreate New Broker Order › Request Body
requestThe literal string "/v1/clearing/broker/new"
The nonce, as described in Private API Invocation
source_counterparty_idA symbol that corresponds with the counterparty sourcing the clearing trade
target_counterparty_idA symbol that corresponds with the counterparty where the clearing trade is targeted
symbolThe symbol of the order
amountQuoted decimal amount to purchase
expires_in_hrsThe number of hours before the trade expires. Your counterparty will need to confirm the order before this time expires.
priceQuoted decimal amount to spend per unit
side"buy" or "sell". This side will be assigned to the source_counterparty_id. The opposite side will be sent to the target_counterparty_id
accountRequired for Master API keys as described in Private API Invocation. The name of the account within the subaccount group. Specifies the broker account on which to place the order. Only available for exchange accounts.
Create New Broker Order › Responses
Successful operation
resultWill return AwaitSourceTargetConfirm, meaning the order is waiting for both the source and the target parties to confirm the order
clearing_idA unique identifier for the clearing order.
List Clearing Trades
Roles
The API key you use to access this endpoint must have the Trader role assigned. See Roles for more information.
The OAuth scope must have clearing:read assigned to access this endpoint. See OAuth Scopes for more information.
Headers
X-GEMINI-APIKEYYour API key
X-GEMINI-SIGNATUREHEX-encoded HMAC-SHA384 of payload signed with API secret
X-GEMINI-PAYLOADBase64-encoded JSON payload
Content-TypeContent-LengthCache-ControlList Clearing Trades › Request Body
requestThe literal string "/v1/clearing/trades"
The nonce, as described in Private API Invocation
timestamp_nanosOnly return transfers on or after this timestamp in nanos
limit_per_accountThe maximum number of clearing trades to return. The default is 100 and the maximum is 300.
accountOnly required when using a master api-key. The name of the account within the subaccount group.
symbolThe trading pair
Only return trades after this timestamp
limit_tradesThe maximum number of trades to return
List Clearing Trades › Responses
Successful operation

