generated: '2026-08-14'
method: searched
source: https://developers.rewardful.com/rest-api/overview
limit_count: 1
verified: '2026-08-14'
verification_note: >-
  Re-verified against the REST API overview on 2026-08-14. The docs state "In most cases the
  API rate limit is 45 requests per 30 second window", that 429 responses carry the
  RateLimit header fields from draft-polli-ratelimit-headers-02, and that Rewardful "may
  reduce limits at any time to prevent abuse". Only one published limit exists; there is no
  per-endpoint or per-plan limit table, and no Retry-After header is documented.
name: Rewardful API Rate Limits
description: Rate limiting details for the Rewardful REST API, including request thresholds per time window and guidance for handling 429 responses.
url: https://developers.rewardful.com/rest-api/overview
specificationVersion: '0.1'
rateLimits:
  - name: Standard Request Rate Limit
    description: The default rate limit applied to all Rewardful REST API endpoints. Requests exceeding this limit receive HTTP 429 responses with RateLimit headers.
    requests: 45
    window: 30
    windowUnit: seconds
    scope: account
    headers:
      - name: RateLimit
        description: Contains rate limit quota information to help clients handle failures and retry requests appropriately.
    errorResponse:
      statusCode: 429
      description: Too Many Requests — returned when the rate limit window has been exceeded. Clients should inspect RateLimit response headers and back off before retrying.
    guidance:
      - Treat rate limits as absolute maximums, not targets.
      - Throttle batch operations to avoid bursting against the limit.
      - Implement exponential backoff when receiving 429 responses.
      - Inspect RateLimit headers to determine reset timing before retrying.