Developer API
Developer API
The external API for connecting other systems to Kuver Books: what it covers, how requests are authenticated and signed, the response envelope, and the products, billing and webhook endpoints.
Updated 20 September 2026
The external API lets another system talk to Kuver Books without a person at the keyboard: an ERP, an accounting package, a logistics provider, your own integration. It is available on the Enterprise plan; see pricing and ask us what you want to connect.
What it covers
- Products: list the catalogue, read low-stock status, update a product, and submit stock adjustment requests that go through the same approval as an adjustment made on screen.
- Billing: list, create and void sales invoices, and list and create credit notes and debit notes.
- Webhooks: have Kuver Books call your server when an invoice is created or voided, or a stock adjustment is approved.
The pages in this chapter
- Introduction: how the gateway works, the response envelope and the status codes.
- Authentication: the headers on every request and the signature on requests that change data.
- Products: the product and stock adjustment endpoints.
- Billing and invoices: the invoice, credit note and debit note endpoints.
- Webhooks: registering an endpoint, the events, verifying the signature and the retry policy.
Before you start
Integration credentials (a client ID, a client secret and, if you register a webhook, a webhook secret) are issued when we set up your integration, together with the base URL for your organisation. Requests are limited to 100 per minute per integration and can be restricted to the IP addresses you list.