Public Error Codes, New Documentation, and AI in the Docs
July's product updates: API errors become predictable and safe to show your users, the documentation gets a full rebuild, and you can now ask the docs anything.
TL;DR
- Public error codes: every API error now returns a stable
codeand a safe-to-displaydescription - New documentation: rebuilt navigation, REST-only quickstarts, and a self-hosted API reference
- AI in the docs: an assistant that knows our entire API and answers instantly
- Idempotency keys: opt-in
Idempotency-Keyheader on all mutating v1 endpoints
Public error codes
Every API error response now includes two additive fields: code, a stable identifier like PAYOUTS_INSUFFICIENT_BALANCE, and description, human-readable text safe to show your end users. Existing responses are unchanged, so nothing breaks.
Each code is documented with its retry semantics, so your integration knows whether to retry, stop, or ask the user to act. Browse the full list in the API reference.
New documentation
We rebuilt blindpay.com/docs from the ground up. Navigation is organized around what you are doing (Payins, Payouts, Send, Receive, Store), and every quickstart is REST-only with managed wallets, so you can integrate without touching blockchain tooling.
The API reference now lives at blindpay.com/docs/api/reference with one URL per endpoint. All old URLs redirect.
AI in the docs
The docs now answer back. An AI assistant trained on our entire documentation and API reference is built into every page: ask "how do I create a payout quote" or paste an error code, and it gives you a direct answer with working request examples, no page hunting.
It is the fastest way to integrate BlindPay. Most questions that used to become support tickets now get answered in seconds, right where you are working.
And this is just the start: the same AI is coming to the dashboard next, where you will be able to run your entire operation by simply asking in plain language.
Idempotency keys
Mutating v1 endpoints now accept an optional Idempotency-Key header. Retry with the same key and you get the original response back instead of a duplicate action, making timeouts and retries safe on payment-creating calls.