Cosmos API
    • Overview
    • Getting started
    • Authentication
    • Environments
    • Rate Limits & Quotas
    • Error Handling
    • Idempotency & State management
    • Forward Compatibility
    • Upsert flight legs
      POST
    • Schemas
      • IngestRequest
      • FlightLeg
      • Delay
      • PassengersPerCabinClass
      • SpecialServices
      • TurnaroundFeedbackCheck
      • IngestResponse
      • MishandledBag
      • IngestResult
      • IngestSummary
      • ValidationError
      • ErrorResponse
    Open appWebsiteStatusLinkedin
    Open appWebsiteStatusLinkedin

    Rate Limits & Quotas

    To ensure platform stability, Cosmos enforces rate limits on API requests.

    Current limits#

    LimitValue
    Requests per minute60 per organization
    Flight legs per request50 (maximum)

    Rate limit response#

    When you exceed the rate limit, the API returns HTTP 429 Too Many Requests with a Retry-After header indicating how many seconds to wait before retrying.
    {
      "errors": [
        {
          "code": "rate_limit_exceeded",
          "detail": null,
          "source": null
        }
      ]
    }
    TIP
    Batch flight legs into single requests (up to 50 per call) rather than sending one leg per request. At 60 requests/minute with 50 legs each, you can ingest up to 3,000 flight legs per minute.

    Recommendations#

    Use the Retry-After header value when backing off on 429 responses
    Implement exponential backoff as a fallback (start at 1s, max 60s)
    Space out bulk data loads rather than sending everything at once
    If you consistently need higher throughput, contact your Cosmos account manager to discuss limit adjustments
    Previous
    Environments
    Next
    Error Handling
    Built with