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: IBM WebSphere
providerId: websphere
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:
  - Application Server
  - Cloud Native
  - Enterprise Java
  - J2EE
  - Rate Limiting
  - Contact Sales
description: IBM WebSphere runs inside the customer's data center / hybrid-cloud footprint; its admin
  REST, JMX, and hosted-application surfaces are not subject to a centrally published rate-limit
  policy. Concurrency, thread-pool sizing, and connection limits are configured by the operator via
  the WebSphere admin console / server.xml.
notes: ibm.com 403 on automated fetch. Limits are deployment-tunable, not provider-published.
sources:
  - https://www.ibm.com/products/websphere-application-server
responseCodes: {}
limits:
  - name: Deployment-Tuned Throughput
    scope: deployment
    metric: varies
    limit: configured per WebSphere cell / server / thread-pool
policies:
  - name: Self-Tuned Limits
    description: WebSphere exposes thread-pool, connection-pool, and JCA / EJB pool tuning that the
      operator configures. There is no public per-call quota imposed by IBM on customer deployments.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com