Crypto.com

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 History Use 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

GitHub OpenAPI

Operations 11

POST /private/otc/request-quote private/otc/request-quote #
POST /private/otc/get-otc-instruments private/otc/get-otc-instruments #
POST /private/otc/get-open-quote-requests private/otc/get-open-quote-requests #
POST /private/otc/get-open-quotes private/otc/get-open-quotes #
POST /private/otc/get-quote-history private/otc/get-quote-history #
POST /private/otc/get-quote-request-history private/otc/get-quote-request-history #
POST /private/otc/request-deal private/otc/request-deal #
POST /private/otc/get-open-deals private/otc/get-open-deals #
POST /private/otc/get-deal-history private/otc/get-deal-history #
POST /private/otc/get-settle-later-limit private/otc/get-settle-later-limit #
POST /private/otc/get-unsettled-amounts private/otc/get-unsettled-amounts #

Documentation

📖
Documentation
https://exchange-developer.crypto.com/exchange/v1/docs/api/rest-introduction
📖
APIReference
https://exchange-developer.crypto.com/exchange/v1/docs/api/rest/crypto-com-exchange-api-v-1
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/authentication/crypto-com-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/rate-limits/crypto-com-rate-limits.yml

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/openapi/crypto-com-otc-rfq-for-taker-api-openapi.yml

Other Resources

🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/conventions/crypto-com-conventions.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/errors/crypto-com-error-codes.yml
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/sandbox/crypto-com-sandbox.yml
🔗
ChangeLog
https://exchange-developer.crypto.com/exchange/v1/docs/api/rest-change-log
🔗
ToolCrosswalk
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/mcp/crypto-com-tool-crosswalk.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/data-model/crypto-com-data-model.yml
🔗
LLMsTxt
https://exchange-developer.crypto.com/exchange/v1/llms.txt

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/crypto-com-otc-rfq-for-taker-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

crypto-com-otc-rfq-for-taker-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Crypto.com Exchange API v1 OTC RFQ for Taker API
  version: 1.0.0
  description: '## Welcome


    Welcome to the Crypto.com Exchange API v1 reference documentation.'
servers:
- url: https://api.crypto.com/exchange/v1
  description: Production
- url: https://uat-api.3ona.co/exchange/v1
  description: UAT Sandbox
tags:


# --- truncated at 32 KB (68 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/crypto-com/refs/heads/main/openapi/crypto-com-otc-rfq-for-taker-api-openapi.yml