Clearway Documentation
  • Home
  • Guides
  • Merchant API
  • Investor Read API
API integration
Getting startedAuthenticationAPI keys and scopesRequest headersIdempotencyErrorsWebhook verificationWebhook eventsOrders and revenueSubscriptionsCheckout integrationDashboard vs APIRate limits
Investor / LP
Investor Read API
Merchant dashboard
Getting startedPayment links & chargesPayment widgetClearway ElementsCheckout & branding
powered by Zudoku
Guides

Errors

Errors

Failed merchant API requests return JSON with success: false, a human-readable error, and a machine code.

Common codes (API key auth)

HTTPCodeMeaning
401UNAUTHORIZEDMissing, invalid, or revoked API key
403FORBIDDENScope denied, account not ready for charges, or function blocked for API keys
403API_GATEWAY_KEY_FORBIDDENFunction is dashboard-only — see Dashboard vs API
429RATE_LIMIT_EXCEEDEDToo many requests — back off and retry
404NOT_FOUNDResource not found (no cross-tenant hints)

Session-only dashboard errors (for example EMAIL_NOT_VERIFIED) are returned when using a Clerk session on dashboard routes — not when calling the merchant HTTP API with an API key. See Dashboard vs API.

Example

Code
{ "success": false, "error": "API key missing required scope (read:orders)", "code": "FORBIDDEN" }

Include an optional x-cid header on requests so support can trace audit logs.

Next steps

  • Authentication — headers and base URL
  • Rate limits — backoff guidance
  • API Reference — per-operation responses
Last modified on July 22, 2026
IdempotencyWebhook verification
On this page
  • Common codes (API key auth)
  • Example
  • Next steps
JSON