Build on Qashio
Qashio API 2.0 gives partners one consistent way to reach company, card and spend data, from ERP master data and card issuance to user invitations and refund mapping, and to keep that data in sync with your own systems.
Your first request
Every request carries a Bearer access token, which you get by runningQashio's OAuth login flow: your user signs in with their Qashio account, approves access, and your server exchanges the resulting code for a token. The token is already bound to that company, so you never send acompanyId or an x-api-key header.
curl -X GET 'https://api.qashio.com/public/v1/erp/company/summary' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <access_token>'Base URL https://api.qashio.com. The API reference lists every environment.
Every response looks the same
Successful responses share one envelope. data holds the resource or collection,pagination appears on list endpoints, and meta.request_id is also returned as the x-request-id header.
{
"status_code": 200,
"success": true,
"data": {},
"pagination": {},
"meta": {
"request_id": "req_a1b2c3d4e5f6",
"timestamp": "2026-07-17T08:00:00.000Z"
}
}Full rules in Requests and responses and Errors.
What you can do
A typical integration
- 1Get credentials
Qashio enables API access and issues your Client ID and Client Secret.
- 2Obtain an access token
Run the OAuth 2.0 authorization code flow and exchange the code at the token endpoint.
- 3Pull master data
Sync suppliers, chart of accounts, tax rates and bank accounts so spend can be coded correctly.
- 4Sync spend
Page through transactions with an updated_at window and post them into your ledger.
The integration walkthrough covers the full sequence, including card issuance and refund mapping.