specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Infor
providerId: infor
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
# Upgraded generated -> searched on 2026-09-13: Infor DOES publish a rate-limit
# policy model for the ION API Gateway (Quota and Throttling endpoint policies),
# just not fixed numbers. The docs URL and the verbatim policy field names are
# now recorded below.
method: searched
source: https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/apigatewaybaasdg/lcs1730257685556.html
docs: https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/apigatewaybaasdg/lcs1730257685556.html
modified: '2026-09-13'
reconciled: false
tags:
  - ERP
  - CloudSuite
  - Industry Cloud
  - Rate Limiting
description: Infor does not publish public per-second rate-limit numbers for its CloudSuite / ION API
  surface. Throughput on a tenant is governed by the contracted environment sizing and Infor OS / ION
  shared-services capacity, with customer-tunable concurrency on the integration adapters. Specific
  TPS values must be obtained from Infor support.
notes: No public Infor rate-limit page reachable. Customers should consult Infor Support / their account
  team for tenant-specific limits and for raising temporary increases.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Tenant API throughput
    scope: tenant
    metric: varies
    limit: governed by contracted CloudSuite environment sizing and ION shared-services capacity
    applies:
      - Infor ION API
      - Infor CloudSuite APIs
policies:
  - name: Backoff Strategy
    description: Clients receiving 429 or 503 should implement exponential backoff with jitter and honor
      Retry-After when present.
  - name: ION Document Flow Throttling
    description: Long-running document flows in Infor ION are queued; tune flow concurrency rather than
      hammering synchronous endpoints.
  - name: Capacity Sizing
    description: Throughput is bounded by the contracted CloudSuite environment; raise capacity by working
      with Infor Support rather than expecting automatic burst.
  - name: Fair Use
    description: Infor reserves the right to throttle traffic that materially impacts shared infrastructure.
# --- Added 2026-09-13 from the Infor OS "API Gateway Endpoint Policies" documentation. ---
# Infor does not publish a single global rate limit. It publishes a POLICY MODEL that a
# tenant administrator configures per API-suite endpoint. The field names below are verbatim
# from that page; no default values are stated anywhere in the documentation.
policyModel:
  source: https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/apigatewaybaasdg/lcs1730257685556.html
  scope: per API suite endpoint, configured by an IONAPI-Administrator on the tenant
  types:
    - name: Quota
      description: Hard cap — allows a request count per interval.
      fields:
        - userLevel
        - interval
        - timeUnit
        - allow
      defaults: not published
    - name: Throttling
      description: Shapes traffic through rate smoothing and spike arrest rather than rejecting outright.
      fields:
        - timePeriodInMilliseconds
        - rateSmoothing.delayAfterCount
        - rateSmoothing.delayFactorInMilliseconds
        - spikeArrest.maxRequestsPerPeriod
      defaults: not published
signaling:
  headers: []
  status_on_exhaustion: not published
  note: >-
    The Infor documentation states neither the HTTP status code nor any response
    headers returned when a Quota or Throttling policy rejects a request, and no
    429 response is declared anywhere in openapi/_original/. An agent therefore
    has NO runtime exhaustion signal it can rely on from the published contract.
    The 429/503 codes recorded under responseCodes above are the generic HTTP
    expectation, not an Infor-published value.
limit_count: 0
limit_count_note: >-
  Zero published numeric limits. Infor publishes the mechanism, not the numbers —
  every concrete value is tenant configuration. Recorded as an honest zero.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com