주제: rate-limiting

• Stripe API pagination and idempotency keys: starting_after, has_more and the 24-hour window

  Stripe's v1 list endpoints paginate with the mutually exclusive starting_after/ending_before cursor parameters (limit 1-100, default 10) and a has_more flag, with client-library auto-pagination helpers to walk every page; POST requests can carry an Idempotency-Key whose saved result Stripe replays for about 24 hours, after which keys may be pruned. Rate-limited requests get 429 with a Stripe-Rate-Limited-Reason header.

  article · en · reviewed · 지식 기준일 2026-09-25

• Following Microsoft Graph's @odata.nextLink and handling 429 throttling and batch limits

  Microsoft Graph pages large collections through an @odata.nextLink URL that must be followed as an opaque token rather than parsed or reconstructed, supports client-driven $top page sizes, throttles with HTTP 429 and a Retry-After header, and limits a single JSON batch request to 20 individual sub-requests.

  article · en · reviewed · 지식 기준일 2026-09-25

• Google API pagination and quota errors: pageToken, 403 rateLimitExceeded and 429

  Google Workspace APIs such as Calendar and Drive page through a pageToken/nextPageToken pair with maxResults (Calendar) or pageSize (Drive), and Drive signals overload two ways: HTTP 403 with reason rateLimitExceeded or userRateLimitExceeded, or HTTP 429 with reason rateLimitExceeded — all documented as cases for retrying with exponential backoff, unlike other 403 reasons.

  article · en · reviewed · 지식 기준일 2026-09-25

• Paging the GitHub REST API and reading its primary and secondary rate-limit headers

  GitHub's REST API paginates via a link header with rel="next"/"last" URLs and a per_page parameter capped at 100 for most endpoints; primary rate limits are reported in x-ratelimit-limit/remaining/used/reset/resource, both primary and secondary limits answer with 403 or 429 (secondary ones sometimes with retry-after), and an authorized conditional GET that returns 304 does not count against the primary limit.

  article · en · reviewed · 지식 기준일 2026-09-25

• Paging the Slack Web API and handling its per-method rate-limit tiers

  Slack's Web API paginates cursor-style through response_metadata.next_cursor and a limit parameter (100-200 recommended, maximum 1000 subject to change and varying per method), and enforces per-method, per-workspace rate-limit tiers from 1+ to 100+ requests per minute, returning HTTP 429 with a Retry-After header in seconds when exceeded.

  article · en · reviewed · 지식 기준일 2026-09-25

• RateLimit and RateLimit-Policy versus X-RateLimit-*: reading whichever quota headers an API sends

  An IETF Internet-Draft (draft-ietf-httpapi-ratelimit-headers-11, May 2026) proposes RateLimit and RateLimit-Policy header fields (e.g. RateLimit: "default";r=50;t=30) to advertise quota ahead of a 429, but it remains a draft; most APIs today send their own x-ratelimit-limit/-remaining/-reset-style headers or nothing beyond Retry-After, which RFC 9110 defines (seconds or an HTTP-date) and RFC 6585 allows on 429.

  article · en · reviewed · 지식 기준일 2026-09-25

기계 판독 가능: JSON