Get OTC Offer by ID

Returns the same object as Get OTC Offer Detail, keyed by the offer's own ID instead of the (token, deal) pair: use it when you hold an offer ID taken from a transaction, a report or a list. Access is checked against the node of the offer's token either way: the node must be inside your API key's node subtree.

Required permission: otc:view

Request

GET /v2/admin/otcs/{otc_id}

Parameters

Name	Type	In	Description
otc_id	string	path	Required. The offer's own ID (24-character hex)

Headers

Name	Description
Authorization	Required. Bearer <access_token>

Example

curl --request GET \
  --url '{{baseUrl}}/v2/admin/otcs/6a8b5d02f9129816a6cc79f4' \
  --header 'Authorization: Bearer <access_token>'

Response

{
  "id": "6a8b5d02f9129816a6cc79f4",
  "token_id": "68ae06cfcccf4e8fc19362d1",
  "node_id": "6810a8e5b45680e7d2f95bad",
  "user_id": "680c02896d91ca0145cfeb81",
  "deal_id": 2,
  "price": {
    "amount": "5",
    "decimal": 6,
    "symbol": "USDT",
    "address": "0x78fccec69e21dc0b331b59f283d4d5b41ff36654"
  },
  "quantity": 1,
  "status": 0,
  "created_at": "2026-08-23T17:41:22.913Z",
  "updated_at": "2026-08-23T17:41:22.913Z",
  "user": {
    "id": "680c02896d91ca0145cfeb81",
    "name": "Ada",
    "surname": "Yılmaz",
    "email": "ada@example.com"
  }
}

Response Fields

The same fields as Get OTC Offer Detail: the offer (id, token_id, node_id, user_id, deal_id, price, quantity, status, created_at, updated_at), the user who made it and the latest transaction acting on it. In the example no accept or cancel has been started yet, so transaction is omitted.

Errors

Status	Code	Description
400	10015	Validation failed — see details. Includes an otc_id that is not a 24-character hex ID
400	11001 (domain 11)	Offer not found
400	10001 (domain 5)	The offer's token was not found
400	10001 (domain 2)	The token's node was not found
403	10005 (domain 2)	The token's node is outside your API key's node subtree
500	10000	Unexpected server error

See Errors for the error format and common codes.