\n\n[](https://snaptrade.com)\n\n# [SnapTrade](https://snaptrade.com)
\n\nConnect brokerage accounts to your app for live positions and trading.\n\n## Rate limiting
\n\nTwo limits apply to requests signed with your `clientId`. The stricter one\nwins, and exceeding either returns `429 Too Many Requests`.\n\n- **Customer-level** — 250 requests/minute by default, scoped to your\n `clientId` and applied across all endpoints. Reported in\n `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`.\n- **Account-level** — 10 requests/minute per account, scoped to\n (`clientId`, `accountId`). All covered operations for one account draw on\n the same bucket — reading balances and reading positions share it — and\n enforcement does not depend on the HTTP method, so updating an account\n consumes the same bucket as reading it. Only enforced for Personal users,\n and only for integrations it has been rolled out to — it is not yet in\n force for every Personal integration. It also does not apply on every\n operation that documents a 429 below. Where it applies it is reported in\n `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and\n `X-RateLimit-Account-Reset`. Do not read the absence of those headers as\n proof the limit is off — some configurations omit the rate limit headers\n while still enforcing the limit, so header absence tells you nothing\n about your allowance.\n\nOn a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit\nand `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for\nthe corresponding `*-Reset` value (seconds) before retrying, or fall back to\nexponential backoff with jitter.\n\nNot every 429 is explained by those headers. A separate\nper-authenticated-user limit, reported in no `X-RateLimit-*` header, covers\nOAuth-authenticated requests and signed requests in configurations where the\ncustomer-level limit is not in effect — on the operations that use the\ndefault throttles. A few operations override those and are governed by the\ncustomer-level limit alone. The two do not stack: a signed request\ngoverned by the customer-level limit above is not additionally subject to the\nper-user one. If a 429 arrives with no header at zero — or with no\n`X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the\nremaining counts as a hint, not a guarantee that the next request will\nsucceed.\n\nBecause the customer-level limit applies everywhere, any signed request can\nreturn 429.\n\n**OAuth-authenticated requests are an exception.** They are not subject to\nthe customer-level limit and do not receive `X-RateLimit-Limit`,\n`X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers\nor design around a customer-level allowance on this path. The account-level\nlimit still applies to them on the account-data endpoints above, reported in\nthe `X-RateLimit-Account-*` headers. On operations using the default\nthrottles the per-user limit above applies to them as well, so an OAuth\nrequest can be rejected while the account headers still show capacity; on\nthe few operations that override those throttles, OAuth callers have no\nper-user ceiling at all. Drive retries from `Retry-After` and exponential\nbackoff with jitter rather than from the headers.\n\nSee https://docs.snaptrade.com/docs/ratelimiting.\n\n\n[](https://www.npmjs.com/package/snaptrade-typescript-sdk/v/12.2.16)\n[](https://snaptrade.com/)\n\n