General Information

Using an AI assistant?

This documentation is also published in an LLM-friendly format:

• llms-full.txt: the whole documentation in one file
• llms.txt: an index of every page, each linked as Markdown

Copy the prompt below into ChatGPT, Claude, Cursor or any other AI tool to get started:

I am integrating with the BtcTurk Global API.
Read the complete documentation from:
https://global.btcturk.com/apidoc/llms-full.txt
Page index:
https://global.btcturk.com/apidoc/llms.txt

Use it as the single source of truth. Do not guess endpoints, parameters or error codes that are not in the documentation.

Then help me with the following:

Welcome to the BtcTurk Global API documentation.

The BtcTurk Global API gives you programmatic access to BtcTurk Global's spot markets: market data, trading and account management over REST, and a WebSocket feed for realtime market data and your own order, trade and balance events.

REST base URL	https://api.global.btcturk.com
WebSocket URL	wss://ws.global.btcturk.com (HTTP/1.1 only, see Connection & Message Format)
Authentication	HMAC-SHA256 with your API key; see Authentication V1
Rate limits	3 requests per 500 ms and 60 per 10 seconds; see Rate Limits
Pair format	BTCUSDT; BTC_USDT is also accepted wherever a pairSymbol parameter is taken
Timestamps	Milliseconds since the Unix epoch, UTC
Support	support@global.btcturk.com

Every path in this documentation is relative to the base URL. For example, GET /api/v2/ticker is https://api.global.btcturk.com/api/v2/ticker.

• For GET endpoints, parameters must be sent as a query string.
• Requests with a body (POST, and DELETE /api/v1/order) must send it as JSON with Content-Type: application/json.
• Parameters can be sent in any order.

Response formats

Responses are JSON. Most endpoints wrap the result in an envelope:

{ "success": true, "message": null, "code": 0, "data": {} }

On success, message can also be "SUCCESS" or an empty string; check success and code. See Error Codes for the error formats.

These endpoints return the result directly as a JSON array or object, without the envelope, and report errors as RFC 7807 problem documents: Get Pairs, Get Currencies, Get Currency Channels, Get Crypto Channels, Crypto Deposit Addresses (list and by id), Crypto Withdrawal Addresses (list and by id), List Crypto Withdrawals, Get Crypto Withdrawal by Id and Get Trade Volumes. Each endpoint page shows its format.

Number formats

Prices, amounts, fees and balances in order, trade, transaction and balance responses are strings, and so are trade ids, so that no precision is lost. Parse them with a decimal type, not a float. Ticker values, preciseAmount, the amounts in List Crypto Withdrawals and Get Crypto Withdrawal by Id, and other ids (order ids, for example) are JSON numbers. Timestamps are integers in milliseconds since the Unix epoch (UTC).