generated: '2026-08-13'
method: searched
source: https://docs.uplead.com/#rate-limit
name: UpLead Rate Limits
description: >-
  API rate limits and throttling for the UpLead v2 API, read verbatim from the
  published Rate Limit section of the documentation. UpLead publishes one limit —
  500 requests per minute per API key — and returns the full legacy
  X-RateLimit-* header trio plus Retry-After on the 429, so the runtime signal an
  agent needs is available on every response, not just at exhaustion. Note that
  the request-rate limit is NOT the binding constraint on this API: credit
  consumption is, and that is recorded in plans/uplead-plans-pricing.yml and
  finops/uplead-finops.yml.
url: https://docs.uplead.com/#rate-limit
limit_count: 1
sample_429_body: >-
  {"error":{"type":"rate_limit","message":"Rate limit exceeded. Limit is 500
  requests per minute. Rate limit will be reset in 50 seconds."}}
limits:
  - name: Standard Rate Limit
    description: Maximum number of API requests allowed per minute
    requests: 500
    period: minute
    scope: per API key

headers:
  - name: X-RateLimit-Limit
    description: The maximum number of requests allowed in the current rate limit window
  - name: X-RateLimit-Remaining
    description: The number of requests remaining in the current rate limit window
  - name: X-RateLimit-Reset
    description: UTC epoch timestamp indicating when the current rate limit window resets
  - name: Retry-After
    description: Number of seconds to wait before retrying after a rate limit error (429 response)

errorCodes:
  - code: 429
    name: Too Many Requests
    description: Rate limit exceeded; check Retry-After header for reset time
  - code: 400
    name: Bad Request
    description: Invalid parameters supplied in the request
  - code: 401
    name: Unauthorized
    description: Invalid or missing API key
  - code: 403
    name: Forbidden
    description: Account is paused or lacks an active subscription