SW4P Documentation
Browse documentation
Rate Limits

Rate Limits

SW4P applies request limits to protect shared settlement infrastructure. Limits vary by route family, key tier, and wallet activity.

Response Headers

When a route is rate-limited through the shared API-key limiter, responses may include:

HeaderMeaning
X-RateLimit-LimitWindow capacity
X-RateLimit-RemainingRemaining requests in the current window
X-RateLimit-ResetWindow reset time
Retry-AfterSeconds to wait before retrying

429 Response

json
{
  "error": "RATE_LIMITED",
  "message": "Too many requests"
}

Retry Rules

  • Retry 429 only after Retry-After when present.
  • Use idempotency keys for transfer-style writes so client retries do not create duplicate settlement attempts.
  • Avoid retry loops on wallet-signature errors. Request a fresh signature or permit when the backend reports nonce, deadline, or signature validation failures.

Current Tier Guide

TierIntended use
Freelocal development and low-volume pilots
Proproduction integrations with moderate steady traffic
Enterprisecustom limits and operator support