Skip to Content
Developer Portal preview — pages marked Draft describe the intended design and are not yet available.
CTRL K
Go to Syper Console
EssentialsRate Limits

Rate Limits

How Syper protects the platform and how to stay within limits.

DraftDescribes the intended design. Not yet available — names, fields and behaviour may change.

Syper limits how many requests a credential can make in a period of time. Exceeding a limit returns HTTP 429.

Staying within limits

  • Retry 429 responses with exponential backoff and jitter.
  • Prefer webhooks or WebSocket over polling.
  • Spread device and agent fleets across separate credentials so one noisy client doesn’t starve others.
  • Cache read-only data such as account metadata.

Specific limits and response headers are documented in the Rate Limits API reference.

Last updated on
ErrorsIdempotency