BOB Gateway

Get user orders (v3 — amounts carry USD).

GET
/v3/get-orders/{user_address}

Authorization

api_key
AuthorizationBearer <token>

In: header

Path Parameters

user_address*string

User address

Query Parameters

cursor?string

Cursor used to fetch the next page, obtained from the response's next_cursor.

limit?integer

Number of orders to request

Range1 <= value

Response Body

application/json

application/json

curl -X GET "https://example.com/v3/get-orders/string"
{  "nextCursor": "string",  "orders": [    {      "depositAddress": "string",      "dstInfo": {        "amount": "string",        "chain": "string",        "token": "string",        "usd": "string"      },      "estimatedTimeInSecs": 0,      "id": "string",      "srcInfo": {        "amount": "string",        "chain": "string",        "token": "string",        "txHash": "string",        "usd": "string"      },      "status": {        "inProgress": {          "pending_btc_payment": null,          "refund_tx": null        }      },      "timestamp": 0    }  ]}

Get an order by id (v3 — amounts carry USD). GET

Previous Page

Get the maximum spendable Bitcoin amount for the given address (v3). GET

Behaviourally identical to v2; exists so the v3 API surface has its own `operationId` (`get_max_spendable_v3`) rather than sharing v2's, which would tag the same operation under both v2 and v3 and break generated clients.