Concur API
SAP Concur runs a broad REST API program at developer.concur.com: expense, invoice, travel, and profile v4 APIs with OAuth 2.0. Access sits behind a paid Client Web Services subscription near $500 per month, and OAuth app enablement must be requested with a business justification.
Frequently asked questions
Concur scores D+ on the API Report Card. SAP Concur runs a broad REST API program at developer.concur.com: expense, invoice, travel, and profile v4 APIs with OAuth 2.0. Access sits behind a paid Client Web Services subscription near $500 per month, and OAuth app enablement must be requested with a business justification.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
SAP Concur is the global market leader in integrated travel, expense, and invoice (AP) management software.
Vertical: Travel & Expense (with adjacent Accounts Payable via Concur Invoice). Pre-trip travel request and approval (Concur Request). Corporate travel booking via the Concur Travel online booking tool (OBT), air, hotel, car, rail, with policy enforcement and preferred-vendor steering.
Dominant. SAP Concur holds approximately 61.91% of the travel-expense-management market, by far the largest single share in the category. Roughly 10,500-10,880 companies are documented as active SAP Concur customers across expense management and travel categories.
Expense reports: header (employee, report name, purpose, dates, currency, totals), line entries (date, vendor, amount, expense type, payment type, attendees, comments, allocations), attached receipt images, policy violations, audit flags, approval history.
Founded in 1993; ~33 years old as of 2026. Concur predates the modern SaaS era (it was, by Tom Tunguz's count, one of the first SaaS companies) and the legacy shows.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.