Skip to content
Developers

Guides

Errors & rate limits

Responses use error, code, and optional action. 400 means invalid input, 401 invalid/expired/revoked key, 403 missing permission or insufficient resource scope, 404 missing/inaccessible resource, 409 conflicting work, 413 oversized body, 429 rate limit, and 503 temporarily unavailable or disabled capability. There is no SQL endpoint. External merchant enrichment remains deployment-gated.

Limits: 300 requests/minute per key, user and client IP per Cloudflare location. User limits are shared with portal/MCP activity. On 429 wait for Retry-After. Request bodies are limited to 64 KiB. Retry transient reads with bounded backoff; do not blindly retry key creation or destructive actions.

The interactive reference talks directly to Banking without a proxy, and does not persist keys in local storage. Cross-origin browser calls are enabled for the docs origin; use a backend for dashboards.

Plan feature limits are additionally enforced in PostgreSQL across portal, MCP and all of a customer's keys. Limits use fixed windows and count admitted attempts, including attempts that subsequently fail. Billing and security recovery remain available.

  • entitlement.access_paused (403): contact support to restore account access.
  • entitlement.feature_disabled (403): the feature is disabled by the current plan or an operator restriction. Review Account → Plan and billing.
  • rate_limit.feature (429): includes feature, plan, retry_after (seconds), and resets_at (UTC), plus the Retry-After header. Wait for the window to reset or change plans; a different key does not create a fresh quota.

The independent edge admission limit still applies. Inspect the current feature allowances in your account; plan changes retain usage in the current window. Paid checkout returns do not grant access until a verified Stripe synchronization confirms the subscription.