Welcome
š Welcome to the Spendesk API documentation, here you'll find helpful guides on how to integrate with us, our API specifications, and details on changes to our APIs.
āļøš If you're not a fan of the current colour scheme, check out the theme toggle in the top right ā
Use cases
The Spendesk API lets you:
- Retrieve spend data ā payables, settlements, bank fees and wallet loads ā and pull it into whatever analytics platform you need to create dashboards, automate accounting or drive insights. See What is Spend Data?
- Keep reference data in sync ā suppliers, users, cost centers, analytical fields and expense categories.
- Automate accounting ā read and maintain the chart of accounts, retrieve purchase and bank journals, and write bookkeeping statuses back to Spendesk (experimental).
- Manage purchasing ā purchase orders, supplier invoices and invoice intake (experimental).
- Follow card spend ā cards, requests and transactions (experimental).
- React to events ā receive webhooks when payables are created or prepared and when settlements are created (experimental).
Endpoints marked experimental require specific scopes: see Scopes.
Where to start
You use Spendesk and want to connect your own tools. Ask your Spendesk representative for API access, create an API key, then follow the Quickstart to make your first call. How to Authenticate covers API keys in detail.
You are building an integration for Spendesk customers. Contact the Spendesk partnerships team. Partner integrations connect with OAuth2: see How to Authenticate.
You want to try the API first. Build and test against the demo environment, https://public-api.demo.spendesk.com, before going live on https://public-api.spendesk.com. Ask for demo credentials when you request API access.
To explore the API reference, a good start is the token endpoint (for simple authorization) and the payables snapshot endpoint for our spend data flow. You can also use our public Postman collection, or download our OpenAPI spec.
Conventions
We follow an API-first mindset and value good API design principles. If you're curious what this means for how our API behaves, check out our policies on authentication, versioning, error handling and more.
Additionally, the team attempts to guarantee an availability of 99% on Spendesk's API. Availability is measured through response latency and error rate.
Support
We are working closely with all onboarded API consumers. If you need help or want to discuss any API topics please send a message to our support at [email protected].