RFQ

RFQ trading API

Connection and authorization flow:

Read the Websocket API description first

Use the auth headers EFX-Key and EFX-Sign when connecting to the WebSocket. If you sign without them, you will need to authorize afterward

1. Connecting to the WS endpoint wss://trade.finerymarkets.com/ws/rfq

Connection response

{ "event": "CONNECTED" }

1. Authorize (if authorization headers were not provided in step 1).

Authorization request

{
"event": "AUTH",
"key": string,
"signature": string,
"content": string
} 

For "content": string refer to Websocket API description

Successful authorization response

{ "event": "AUTHORIZED" }

Trading flow:

Endpoint for trading: wss://trade.finerymarkets.com/ws/rfq

1. Send the RFQ session request event to create an RFQ session. The server responds with Successful RFQ session response, indicating that the RFQ session has been created. The service sends requests to external providers (from the list specified by the client in the request). Upon receiving an answer from any provider, the server sends a Quote response.

RFQ session request

{
"event": "CREATE",
"reqId": int,
"instrument": string,
"providers": int[],
"side": string ("BUY"/"SELL"),
"size": int,
"clientId": int (optional, required only if request is authorized)
}

For getting providers use:

getProviders

Successful RFQ session response

{ "event": "CREATED", "reqId": int }

Quote response

{
"event": "QUOTE",
"reqId": int,
"status": string, ("SUCCESS", "REJECT", "ERROR")
"expiresAt": datetime,
"providerId": int,
"quotes": [
   {
     "side": string ("BUY"/"SELL"),
     "price": int 
   } 
 ],
"error": string
}

1. Send an Order confirmation request to approve the deal with the provider specified in the request. The server sends another request to the specified provider, and depending on its response, the server can respond with an Order confirmation response with different statuses:

   • SUCCESS if the provider approved the deal.

   • REJECT if the provider rejected the deal.

   • ERROR if there was an error during the request.

Order confirmation request

{
"event": "COMMIT",
"reqId": int,
"providerId": int,
"side": string ("BUY"/"SELL")
}

Order confirmation response

{
"event": "COMMITTED",
"reqId": int,
"status": string, ("SUCCESS", "REJECT", "ERROR"),
"error": string
}

RFQ session statuses include:

• CREATED – The session has been initialized.

• COMMITTED – The session has been successfully finished with the committed order.

• CANCELED – The session was canceled.

• EXPIRED – The session expired without commitment.

• REJECTED – Commitment to the LP was rejected due to insufficient trading limits or other risk management checks.

• FAILED – The commitment to the LP failed due to technical errors or issues during processing.

1. Send a Cancel request to cancel the RFQ completely. After you will receive Cancel response from the server. Then the RFQ session may be restarted.

Cancel request

{
"event": "CANCEL",
"reqId": int
}

Cancel response

{
"event": "CANCELED",
"reqId": int
}

1. If an internal error occurs, you will receive an Error response event.

Error response

{
"event": "ERROR",
"reqId": int,
"error": int,
"errors": string
}