SAP Concur
SAP Concur provides a comprehensive suite of REST APIs for travel, expense, and invoice management. The Concur API platform enables integration with expense reporting, travel booking, invoice processing, receipt capture, and user management services used by enterprises worldwide for spend management automation.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles SAP Concur the way a machine reads it — 51 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SAP Concur scores 63.7/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile SAP Concur
Each block below is one kind of artifact we hold for SAP Concur. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SAP Concur Expense API
REST API for managing expense reports, entries, allocations, and attendees. Supports creating, updating, and submitting expense reports with receipt images, policy validation, a...
SAP Concur Travel API
REST API for managing travel itineraries, bookings, and travel profiles. Supports searching for travel options, creating bookings, and managing travel policies and preferences.
SAP Concur Invoice API
REST API for accounts payable invoice processing including purchase requests, vendor management, payment batches, and invoice approval workflows.
SAP Concur Receipts API
REST API for submitting and managing digital receipts from e-commerce providers, ground transportation, hotels, and other merchants directly to Concur expense.
SAP Concur Request API
REST API for managing pre-trip travel requests and approvals, enabling employees to submit travel requests for authorization before booking.
SAP Concur User Provisioning API
SCIM 2.0-compliant API for provisioning and managing Concur user accounts, roles, and profile information with support for bulk operations.
SAP Concur Events API
Event subscription API enabling applications to receive real-time notifications when events occur in Concur such as expense report submissions, approvals, and status changes.
SAP Concur Lists API
REST API for managing custom lists and list items used in expense forms, travel policies, and invoice configurations for dropdown and lookup fields.
SAP Concur Expense Reports API
Manage expense reports
SAP Concur Expenses API
Manage individual expense entries
Scroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Concur Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Concur Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Concur Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Expense Report Management
Create, submit, and manage expense reports with policy validation and multi-level approval workflows.
Receipt Digitization
Capture and process digital receipts from merchants for automatic expense matching.
Travel Booking Integration
Search and book travel through API-connected travel management companies and booking tools.
Invoice Processing
Automate accounts payable workflows with purchase requests, vendor management, and payment processing.
Event Notifications
Real-time event subscriptions for expense, travel, and invoice status changes.
SCIM User Provisioning
Standards-based user provisioning and management with SCIM 2.0 protocol support.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Concur Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
SAP Concur API Rules
SPECTRALSAP Concur API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ExpenseReport
JSON SCHEMAExpense
JSON SCHEMAExpense
JSON SCHEMAExpenseCollection
JSON SCHEMAExpenseCreate
JSON SCHEMAExpenseReport
JSON SCHEMAExpenseReportCollection
JSON SCHEMAExpenseReportCreate
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Concur Expense Api Expense Report Structure
JSON STRUCTUREConcur Expense Api Expense Structure
JSON STRUCTUREConcur Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
ERP Integration
Integrate Concur expense and invoice data with ERP systems for automated financial posting.
Travel Management
Build travel booking integrations connecting corporate travel policies with booking engines.
Receipt Automation
Automatically capture and match digital receipts from e-commerce and travel merchants.
Spend Analytics
Extract expense and travel data for spend analytics, compliance reporting, and budget tracking.
Employee Onboarding
Automate Concur user provisioning as part of employee onboarding workflows.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SAP S/4HANA
Financial posting integration for automated expense and invoice data transfer to SAP ERP.
SAP SuccessFactors
HR integration for employee data synchronization and travel policy assignment.
Uber for Business
Automated ride receipt submission from Uber business accounts to Concur expense.
Lyft
Ground transportation receipt integration for business ride expense automation.
Microsoft Teams
Approval and notification integration for expense workflows within Teams.
Resources
Every other property we hold for SAP Concur — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/concur · machine-readable index on apis.io