name: Checkmarx 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: Checkmarx providerId: checkmarx 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: - Rate Limiting - Application Security - SAST - SCA description: Checkmarx One does not publish numeric per-second API rate limits in its public documentation. Limits are tenant-scoped and governed by tenant tier and underlying scan-engine concurrency. Self-managed CxSAST deployments inherit limits from the customer's own infrastructure. notes: No public per-second/per-minute rate limit numbers published; tenant-governed. sources: - https://checkmarx.com/resource/documents/en/34965-8158-rest-api.html - https://docs.checkmarx.com/ responseCodes: throttled: 429 unauthorized: 401 serviceUnavailable: 503 limits: - name: Checkmarx One REST API (per tenant) scope: tenant metric: varies limit: see tenant tier / contract - name: Concurrent scans scope: tenant metric: concurrent_scans limit: see tenant tier / contract - name: Self-managed CxSAST scope: deployment metric: varies limit: bounded by customer-managed infrastructure policies: - name: OAuth 2.0 description: Checkmarx One REST APIs use OAuth 2.0 access tokens issued via the tenant identity provider; tokens are scoped to tenant resources. - name: Backoff Strategy description: Use exponential backoff with jitter on 429/503 responses; honor Retry-After when present. - name: Scan queueing description: Scans beyond the concurrent-scan ceiling are queued; consumers should poll for status rather than retry submission. maintainers: - FN: Kin Lane email: kin@apievangelist.com