Saltar al contenido principal

Merchant API Reference

7 endpoints for merchant operations: online/offline status, business open/close, and rest mode. One endpoint uses the adaptive auth pattern.

EP-24: Adaptive Auth Pattern

getAdDetails (merchant view) uses the same two-stage authentication as EP-13:

  1. Attempt 1 — unsigned: GET with X-MBX-APIKEY header only
  2. On 401 / 403 / -1021 / -1022: time sync, then retry with full HMAC-SHA256 signature

Business Status vs. Online Status

Binance C2C has two distinct merchant status layers. Mixing them up causes ads to remain unreachable.

Overall P2P Status

Controls whether the merchant account participates in P2P trading at all.

startBusiness/closeBusiness

EP-27 / EP-22

Online / Offline Status

Controls ad visibility. Merchant must be online for ads to appear in search.

getOnline/getOffline

EP-26 / EP-25

Rest Mode and Errors 83229 / 83230

Rest mode is a "taking a break" status distinct from going offline. When a merchant is in rest mode, order operations return specific errors:

83229

Merchant in rest — ad marked paused

83230

Rest not ended — check ad status

Use startRest (EP-28) and endRest (EP-23) to control this state.

Endpoints

HMAC-SHA256From PDF
HMAC-SHA256From PDF
AdaptiveAutoP2P Verified
HMAC-SHA256From PDF
HMAC-SHA256From PDF
HMAC-SHA256From PDF
HMAC-SHA256From PDF

Related

Error Codes (83229 / 83230)·Rate Limiting Guide·Orders Reference
← OrdersChat →