name: Axway API Rate Limits 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: Axway providerId: axway 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. method: generated modified: '2026-05-05' reconciled: false tags: - API Management - Enterprise - Integration - Security - Rate Limiting description: Axway does not publish global rate limits for its products. Rate limits in Axway-managed APIs are configured by the customer through API Manager / Amplify policies and depend on the deployment. No public Axway-hosted SaaS rate-limit table exists; consumers should consult their tenant administrator or Axway support for tenant-specific quotas. notes: Limits are deployment-defined rather than provider-published. Captured here as configurable rather than fixed. sources: - https://docs.axway.com - https://www.axway.com/en/products/api-management responseCodes: throttled: 429 serviceUnavailable: 503 limits: - name: Tenant-configured throttling scope: api-key metric: varies limit: see API Manager / Amplify policy configuration - name: Per-deployment infrastructure capacity scope: deployment metric: varies limit: see Axway support for negotiated tenant limits policies: - name: Customer-defined throttling description: Throttling, quota, and burst policies are defined by the customer in Axway API Manager / Amplify Engage, not centrally published by Axway. - name: Backoff description: Clients should implement exponential backoff with jitter when receiving 429 or 503 responses. - name: Fair Use description: Sustained usage that materially impacts shared SaaS infrastructure may be subject to fair-use throttling on Amplify-hosted services. maintainers: - FN: Kin Lane email: kin@apievangelist.com