The API Report CardAPI Index
SAP Concur

SAP Concur API

Travel & Expense Management · concur.com

SAP Concur documents OAuth 2.0 REST APIs at developer.concur.com, but production access requires purchasing the paid Client Web Services offering, and SAP must enable the OAuth app management tool per entity. No self-serve signup or first-party SDKs; enablement is effectively sales gated.

Last verified: July 2026Enterprise Software
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented OAuth 2.0 REST APIs at developer.concur.com; the friction is in paid access gating, not the API's existence.
AccessPOORProduction requires the paid Client Web Services offering, and SAP must enable OAuth app tooling per entity.
CoveragePOOR
AuthGOODModern OAuth 2.0 across the REST APIs, with flows documented at developer.concur.com.
Docs & DXGOODREST reference material is public at developer.concur.com and readable before any contract.
StabilityMIXEDPre-2017 authorization paths are deprecated; older integrations must migrate to the current OAuth 2.0 model.
Supergood: SAP Concur has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

SAP Concur scores D on the API Report Card. SAP Concur documents OAuth 2.0 REST APIs at developer.concur.com, but production access requires purchasing the paid Client Web Services offering, and SAP must enable the OAuth app management tool per entity. No self-serve signup or first-party SDKs; enablement is effectively sales gated.

Tried to integrate with SAP Concur?
SOURCES
OAuth app tooling must be enabled by SAP per entity developer.concur.com
Authentication model complex; pre-2017 paths deprecated developer.concur.com
Clunky, dated UI and slow workflows g2.com
Expensive and complex to administer g2.com
Difficult API/integration enablement developer.concur.com