Crypto.com OTC RFQ for Taker API
OTC RFQ (Request For Quote) enables takers to request block trade quotes from multiple liquidity providers, evaluate received quotes, and execute trades at the best available price. This workflow is designed for institutional clients who need to trade large sizes with minimal market impact.## RFQ Trading Flow**Step 1 — Request a Quote**Call the request-quote endpoint to create a new quote request. Key parameters include:- `cl_quote_req_id` — Client-assigned quote request ID for tracking- `firm_quote` — Whether quotes should be firm (guaranteed execution) or indicative- `settlement_arrangement` — `IMMEDIATE` for instant settlement- `duration` — How long the quote request remains open (milliseconds)- `quote_ttl` — Time-to-live for received quotes (milliseconds)- `leg_list` — Array of instruments to trade (supports multi-leg combo trades)The response returns a `quote_req_id` that identifies this request in subsequent calls.**Step 2 — Monitor Incoming Quotes**As liquidity providers respond to your quote request, you can retrieve quotes via REST polling or WebSocket subscriptions. Each quote includes `bid` and `ask` prices, available quantities, and an expiration time.**WebSocket Subscriptions (Recommended):**Subscribe to real-time quote updates for lower latency:- Quote request status updates- Quote updates from makers- Deal execution updates**Step 3 — Accept a Quote**Call the request-deal endpoint to execute the trade with the best available quote. Required parameters:- `deal_type` — Set to `QUOTE_REQUEST` for RFQ flow- `cl_deal_id` — Client-assigned deal ID for tracking- `quote_id` — The ID of the quote you're accepting- `quote_req_id` — The original quote request ID- `leg_list` — Must match the quote's instrument, price, quantity, and side## Quote Request Lifecycle| Status | Description ||--------|-------------|| `NEW` | Quote request created, not yet sent to makers || `ACTIVE` | Quote request sent to makers, awaiting responses || `COMPLETED` | Quote accepted and deal executed || `REJECTED` | Quote request rejected |## Quote Lifecycle| Status | Description ||--------|-------------|| `ACTIVE` | Quote is valid and can be accepted || `EXPIRED` | Quote has exceeded its TTL || `CANCELED` | Maker canceled the quote || `FILLED` | Quote was accepted and executed |## Deal HistoryUse the deal history endpoint to retrieve executed trades. Deal statuses:| Status | Description ||--------|-------------|| `ACCEPTED` | Deal request accepted by the system. || `CONFIRMED` | Liquidity provider has executed the deal. || `SETTLED` | Deal settled and funds transferred. || `REJECTED` | Deal request rejected (quote expired, insufficient balance, etc.) |## Best Practices- **Use WebSocket subscriptions** for production systems to receive real-time quote updates- **Monitor quote expiration times** to avoid accepting stale quotes- **Track client IDs** (`cl_quote_req_id`, `cl_deal_id`) for reconciliation and audit purposes
Crypto.com OTC RFQ for Taker API is one of 14 APIs that Crypto.com publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include OTC RFQ for Taker. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, rate-limit docs, and a changelog.
This API exposes 11 operations across 11 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against 2 base URLs: https://api.crypto.com/exchange/v1, https://uat-api.3ona.co/exchange/v1.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 11
Across 11 paths, the API surfaces 11 operations — 11 POST. Each is listed below with its method, path, parameters, and response codes.
OTC RFQ (Request For Quote) enables takers to request block trade quotes from multiple liquidity providers, evaluate received quotes, and execute trades at the best available pric…
Schemas 22
The contract defines 22 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Crypto.com 12
Other APIs Crypto.com publishes across the network.
This is an independent, third-party profile of Crypto.com OTC RFQ for Taker API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.