“4. Ramp – particularly strong developer experience, although primarily US-focused.”
“- Extensive API documentation.”
“- Public OpenAPI specification.”
“- Client credentials for internal server-to-server integrations.”
“- OAuth2 for third-party integrations.”
“- Granular API permissions.”
“- Webhooks with signature verification and retry handling.”
“- Sandbox access.”
“- Cursor-based pagination.”
“- APIs for bills, cards, transactions, users, reimbursements and procurement.”
“It also supports two-way ERP integrations.”
“4 | Ramp | Excellent developer experience, subject to geographic suitability”
“The main concern is its US-centric product and market focus, which makes it less obvious as a choice for a German or European business.”
“6. SAP Concur – extensive enterprise integration capabilities, but potentially more complex to implement.”
“It offers extensive enterprise integration capabilities, particularly around:”
“- Expense reports.”
“- Employee and organisational data.”
“- Travel bookings.”
“- Financial and accounting information.”
“- Enterprise authentication and authorisation.”
“However, its API ecosystem is more complex than the modern REST-first platforms.”
“2. Spendesk – strong API offering and good coverage of finance workflows.”
“- Extensive API documentation.”
“- Spend data retrieval.”
“- Supplier and employee reference data.”
“- Cost centres and analytical fields.”
“- Accounting and bookkeeping information.”
“- Purchasing and card-related information.”
“- Webhooks.”
“- Different authentication options for customers and integration partners.”
“It also provides demo credentials for development and testing.”
“1 | Spendesk | Strong API coverage and integration options”
“3. Moss – worth considering for a Germany-based finance stack.”
“- Versioned REST API.”
“- Predictable resource-oriented endpoints.”
“- Standard JSON requests and responses.”
“- Expenses, card transactions, invoices and reimbursements.”
“- User and supplier information.”
“- Accounting dimensions and chart of accounts.”
“- Pagination and rate-limit information.”
“The API uses a conventional /v1 structure, which makes it relatively straightforward for developers familiar with REST.”
“2 | Moss | Interesting German-market option and conventional REST API”
“5. Brex – good API capabilities, particularly for cards and spend controls.”
“- OpenAPI-based documentation.”
“- REST and JSON.”
“- OAuth2 authentication.”
“- Granular scopes and permissions.”
“- Webhooks.”
“- Accounting, expenses, budgets, cards, users and payments APIs.”
“One caveat: its expense update API has limited functionality.”
“For example, updating an expense's memo is supported, but updating its category through that endpoint is not.”
“1. Payhawk – particularly interesting for European companies.”
“- REST API with standard HTTP methods.”
“- JSON-based data exchange.”
“- Real-time webhooks.”
“- Access to expenses, transactions, cards and employees.”
“- Custom fields and accounting information.”
“- API access included in all Payhawk accounts.”
“- Published rate limit of 15 requests per second.”
“3 | Payhawk | Good European coverage and real-time integration”
“Important limitation: Payhawk explicitly states that creating and reviewing expenses isn't supported through its API.”
