snaptrade
Connect brokerage accounts to your app for live positions and trading. ## Rate limiting Two limits apply to requests signed with your `clientId`. The stricter one wins, and exceeding either returns `429 Too Many Requests`. - **Customer-level** — 250 requests/minute by default, scoped to your `clientId` and applied across all endpoints. Reported in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. - **Account-level** — 10 requests/minute per account, scoped to (`clientId`, `accountId`). All covered operations for one account draw on the same bucket — reading balances and reading positions share it — and enforcement does not depend on the HTTP method, so updating an account consumes the same bucket as reading it. Only enforced for Personal users, and only for integrations it has been rolled out to — it is not yet in force for every Personal integration. It also does not apply on every operation that documents a 429 below. Where it applies it is reported in `X-RateLimit-Account-Limit`, `X-RateLimit-Account-Remaining` and `X-RateLimit-Account-Reset`. Do not read the absence of those headers as proof the limit is off — some configurations omit the rate limit headers while still enforcing the limit, so header absence tells you nothing about your allowance. On a 429, `X-RateLimit-Remaining: 0` means you hit the customer-level limit and `X-RateLimit-Account-Remaining: 0` means the account-level one. Wait for the corresponding `*-Reset` value (seconds) before retrying, or fall back to exponential backoff with jitter. Not every 429 is explained by those headers. A separate per-authenticated-user limit, reported in no `X-RateLimit-*` header, covers OAuth-authenticated requests and signed requests in configurations where the customer-level limit is not in effect — on the operations that use the default throttles. A few operations override those and are governed by the customer-level limit alone. The two do not stack: a signed request governed by the customer-level limit above is not additionally subject to the per-user one. If a 429 arrives with no header at zero — or with no `X-RateLimit-*` headers at all — honour `Retry-After` and back off. Treat the remaining counts as a hint, not a guarantee that the next request will succeed. Because the customer-level limit applies everywhere, any signed request can return 429. **OAuth-authenticated requests are an exception.** They are not subject to the customer-level limit and do not receive `X-RateLimit-Limit`, `X-RateLimit-Remaining` or `X-RateLimit-Reset` — do not wait on those headers or design around a customer-level allowance on this path. The account-level limit still applies to them on the account-data endpoints above, reported in the `X-RateLimit-Account-*` headers. On operations using the default throttles the per-user limit above applies to them as well, so an OAuth request can be rejected while the account headers still show capacity; on the few operations that override those throttles, OAuth callers have no per-user ceiling at all. Drive retries from `Retry-After` and exponential backoff with jitter rather than from the headers. See https://docs.snaptrade.com/docs/ratelimiting.
View on Github
Activity
- Latest release
- 3d ago
- Total releases
- 269
- Cadence
- ~daily
- Last 12 months
- 100
Reach
- Downloads
- 216.9k
- Stars
- 54
Details
- License
- MIT
- First release
- May 31, 2023
| Version | Released | |
|---|---|---|
3.0.20
patch
| ||
3.0.19
patch
| ||
3.0.18
patch
| ||
3.0.17
patch
| ||
3.0.16
patch
| ||
3.0.15
patch
| ||
3.0.14
patch
| ||
3.0.13
patch
| ||
3.0.12
patch
| ||
3.0.11
patch
| ||
3.0.10
patch
| ||
3.0.9
patch
| ||
3.0.8
patch
| ||
3.0.7
patch
| ||
3.0.6
patch
| ||
3.0.5
patch
| ||
3.0.4
patch
| ||
3.0.3
patch
| ||
3.0.2
patch
| ||
3.0.1
patch
| ||
3.0.0
major
| ||
2.1.0
minor
| ||
2.0.218
patch
| ||
2.0.216
patch
| ||
2.0.217
patch
| ||
2.0.215
patch
| ||
2.0.214
patch
| ||
2.0.213
patch
| ||
2.0.212
patch
| ||
2.0.210
patch
| ||
2.0.211
patch
| ||
2.0.209
patch
| ||
2.0.208
patch
| ||
2.0.207
patch
| ||
2.0.206
patch
| ||
2.0.205
patch
| ||
2.0.204
patch
| ||
2.0.203
patch
| ||
2.0.202
patch
| ||
2.0.201
patch
| ||
2.0.200
patch
| ||
2.0.199
patch
| ||
2.0.198
patch
| ||
2.0.197
patch
| ||
2.0.196
patch
| ||
2.0.195
patch
| ||
2.0.194
patch
| ||
2.0.193
patch
| ||
2.0.192
patch
| ||
2.0.190
patch
|