Coinw Spot Skill

Coinw Spot REST API skill: covers market data, order placement/cancellation, order queries, account balances, and asset transfers.

Setup Credentials

CoinW private endpoints require api_key and a request signature (sign).

Signing note: Spot endpoints use Spot MD5 uppercase signing. Do not use Contract HMAC-SHA256 signing for Spot APIs.

1. Environment variables:

export COINW_API_KEY="your_api_key"
export COINW_SECRET_KEY="your_secret_key"

2. In chat: provide api_key/secret_key (and an account name). The agent will mask secrets when showing them back and store them securely in OpenClaw's credential storage (not inside skill markdown files).

Key Features

• Market data: trading pairs, 24h summary, order book, recent trades, K-line data, hot volume stats
• Trading actions: place order, cancel order / cancel all orders
• Query and account: order query, trade history, spot balances, asset transfer

Quick Reference

Market Information

Place Orders

Query Orders

Account Information

Common Parameters and Enums

Auth and URL

• Base URL: https://api.coinw.com.
• Public REST: GET/POST https://api.coinw.com/api/v1/public?command=....
• Private REST: usually POST https://api.coinw.com/api/v1/private?command=..., with api_key and sign (MD5, see Reference) in query/body.
• Some docs show /v1/private?command=... alongside /api/v1/private; follow actual implementation.

command values (private/public endpoints covered in this file)

cancelAllOrder, cancelOrder, doTrade, getBatchHistoryOrders, getUserTrades, return24hVolume, returnBalances, returnChartData, returnCompleteBalances, returnOpenOrders, returnOrderBook, returnOrderStatus, returnOrderTrades, returnSymbol, returnTicker, returnTradeHistory, returnUTradeHistory, spotWealthTransfer

Common request fields

• symbol / currencyPair: trading pair, for example BTC_USDT (field names vary by endpoint).
• isMarket: market-order related; type: order type; rate / amount / funds: price, quantity, or amount (see order placement section).

Standard response wrapper (common in REST)

• Common top-level fields: code, msg / message, success, failed, data (actual response varies by endpoint).

Common enums

• failed: true/false; indicates whether request failed.
• isFrozen: freeze status: 0 = no, 1 = yes.
• side：BUY/SELL
• state: pair status: 1 = active, 2 = disabled.
• status: 1 = unfilled, 2 = partially filled, 3 = fully filled, 4 = user canceled; order status may also include 5 = triggered, 6 = trigger failed.
• success: true/false; indicates whether request succeeded.
• type (orders, such as in batch history): LIMIT, MARKET, HL_LIMIT, PLANNING, STOP_LIMIT_ORDER, SMART_MARKET_ORDER, ICEBERG, etc.

Examples

GET (public endpoint)

curl "https://api.coinw.com/api/v1/public?command=returnSymbol"

Auth required (private endpoint)

params="api_key=$COINW_API_KEY&amount=0.001&funds=1&isMarket=1&out_trade_no=1&rate=40000&symbol=BTC_USDT"
sign_string="$params&secret_key=$COINW_SECRET_KEY"
sign=$(echo -n "$sign_string" | openssl md5 | cut -d' ' -f2 | tr '[:lower:]' '[:upper:]')
curl -X POST "https://api.coinw.com/api/v1/private?command=doTrade&$params&sign=$sign"

Security

When showing credentials to users:

• API Key: Show first 4 + last 5 characters: 12&*1...198I
• Secret Key: Always mask, show only last 4: ***...isf1
• Ask for user confirmation before any trade action.
• Store user api_key and secret_key in a secure location.

Agent Behavior

1. Credentials requested: Mask secrets (show last 5 chars only)
2. Listing accounts: Show names never keys
3. New credentials: Prompt for name, signing mode

Adding New Accounts

When user provides new credentials:

• Ask for account name
• Store the provided credentials in OpenClaw's secure credential store with masked display confirmation

Reference

• Authentication./references/Authentication.md
• errorcode: ./references/error-codes.md
• notes: ./references/notes.md
• api-key create steps: ./references/api-key-creation-steps.md