Changelog

What changed in Qashio API 2.0, and what moved from the v1 connector.

API 2.0

API 2.0 consolidates the ERP connector and the card/user operations behind one host and one auth model. If you are coming from the v1 connector, these are the changes that matter.

One token, one company

v1 required a company identifier alongside the credential. In 2.0 the access token is the company context: no companyId, no x-api-key. A resource belonging to another company returns 404.

New host and path layout

	v1 connector	API 2.0
Production host	`https://erp.qashio.com`	`https://api.qashio.com`
EU host	`https://erp.qashio.eu`	`https://api.qashio.eu`
Sandbox	`https://erp.qashio.io`	`https://api.qashio.io`
ERP reads	`/erp-suppliers`	`/public/v1/erp/suppliers`
Card and user writes	:	`/public/v1/core/...`

Paths are versioned under /public/v1. ERP reads live under /public/v1/erp/, and card, user and spend actions live under /public/v1/core/.

Path mapping from v1

v1	API 2.0
`GET /erp-bank-accounts`	`GET /public/v1/erp/bank_accounts`
`GET /erp-chart-of-accounts`	`GET /public/v1/erp/chart_of_accounts`
`GET /erp-suppliers`	`GET /public/v1/erp/suppliers`
`GET /erp-tax-rates`	`GET /public/v1/erp/tax_rates`
`GET /erp-transactions`	`GET /public/v1/erp/transactions`
`GET /cards`	`GET /public/v1/erp/cards`
`GET /pool-accounts`	`GET /public/v1/erp/pool_accounts`
`GET /statements`	`GET /public/v1/erp/statements`
`GET /company/summary`	`GET /public/v1/erp/company/summary`

Note the separator change: v1 used hyphens in resource names, 2.0 uses underscores.

Capabilities added in 2.0

Card issuance and control: create a card, update its top-up target and maximum balance, apply or change a velocity limit, and suspend a card.
User invitations: invite users into Qashio by email.
Refund and reversal mapping: resolve a refund or reversal back to its original purchase by filtering ERP transactions on parent_qashio_id.
OAuth endpoints: issue, refresh and validate tokens at /oauth2/token and /oauth2/validate.

Response envelope

2.0 standardises the envelope across every endpoint: status_code, success, data, pagination on lists, message on writes, and meta.request_id everywhere. See Requests and responses.

v1 connector

The v1 connector remains available for existing integrations and is documented under v1 (Legacy). New integrations should build against 2.0.