Get help

If you've checked Troubleshooting and you're still stuck — or you hit an error the docs mark as "not fixable client-side" — reach out directly. We'd rather answer a question in five minutes than have you stall on a dead end.

Contact channels

Use WhatsApp for "why is this call failing right now" — it's the fastest way to get a human who can look at logs with you. Use email for anything that needs a paper trail, isn't urgent, or involves account/billing changes.

What to include when you reach out

The faster you give us this, the faster we can help — most integration issues are solved in one round trip if we have all of it up front:

• Request method and path — e.g. POST /api/v1/safe-catalog/orders.create
• Timestamp and nonce used on the failing request (from your X-Timestamp / X-Nonce headers)
• Response code and code from the error body (e.g. 401 INVALID_SIGNATURE)
• App ID and environment — staging or production

If it's a signature or payload issue, also paste the exact canonical string you built (see Authentication and signing) — most INVALID_SIGNATURE reports turn out to be a mismatch between what was signed and what was sent, and the canonical string shows that immediately.

What to expect

• We read and respond to WhatsApp during business hours, same day for most questions.
• Production activation requests (see Getting started) are a short manual review, not an automated approval — expect a human to follow up if anything's missing from your KYC submission.
• Account status changes (PARTNER_INACTIVE) and anything involving money movement (wallet, syndicated orders) are handled by a person, not resolved automatically — reach out rather than retrying.

Related pages

• Troubleshooting — check here first; most error codes are self-serviceable.
• FAQ — quick answers to common questions.
• How money works — for pricing/refund questions, this is where we point you to ask us directly.