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: SAP Concur
providerId: concur
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:
  - Expense Management
  - Finance
  - Invoice
  - SAP
  - Travel
  - Rate Limiting
description: SAP Concur does not publish specific public per-second / per-minute API rate limits. Throttling
  is applied at the platform level and clients are expected to handle 429 responses with backoff. Limits
  are configured per customer contract / partner agreement (Concur Connect, App Center). Use the developer
  portal for endpoint-specific guidance.
notes: Rate-limit numbers in this file are placeholders pointing to the docs portal because SAP Concur
  does not publish specific RPS/RPM thresholds publicly. Reconcile against an active partner contract
  or via a support case for production-relevant numbers.
sources:
  - https://developer.concur.com/api-reference/
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Platform Throttling
    scope: account
    metric: varies
    limit: 'see SAP Concur developer portal / partner contract'
    notes: Concur applies platform-level throttling per tenant. Specific RPS/RPM thresholds are not publicly
      published; clients should handle 429 responses with exponential backoff.
  - name: Per-Endpoint Quotas
    scope: account
    metric: varies
    limit: 'varies by endpoint and product (Expense, Travel, Invoice, Request)'
    notes: Individual endpoints may impose their own quotas (e.g. bulk export, batch user provisioning).
      Refer to per-endpoint documentation.
policies:
  - name: Backoff Strategy
    description: Implement exponential backoff with jitter on 429 and 503 responses.
  - name: Authentication
    description: All Concur APIs require OAuth2 access tokens issued via the company / app credential
      flow; tokens are scoped per tenant and expire on the platform's standard schedule.
  - name: Sandbox vs Production
    description: Implementation testing happens in the Concur Implementation environment (CTE / sandbox)
      where rate limits may differ from production.
  - name: Partner Program
    description: API access is gated through the SAP Concur App Center / Concur Connect partner program;
      raised limits are negotiated through the partner relationship rather than self-serve.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com