API reference
Resources
The main read endpoints, all under https://api.kumry.com. Each is a GET request authenticated with an API key.
Contacts and accounts
| Endpoint | Returns |
|---|---|
| GET/contacts | Customers and suppliers. |
| GET/accounts | The chart of accounts. |
Sales and purchases
| Endpoint | Returns |
|---|---|
| GET/invoices | Sales invoices. |
| GET/bills | Supplier bills. |
Banking
| Endpoint | Returns |
|---|---|
| GET/banking/accounts | Bank accounts held in Kumry. |
| GET/banking/transactions | Bank transactions from statement imports. |
Reports
| Endpoint | Returns |
|---|---|
| GET/reports/profit-and-loss | Profit and loss. |
| GET/reports/balance-sheet | Balance sheet. |
| GET/reports/trial-balance | Trial balance. |
| GET/reports/aged-receivables | Aged receivables. |
| GET/reports/aged-payables | Aged payables. |
| GET/reports/gst-summary | GST summary for a period. |
Writing data
A key with write access can create and update records where an editor can. Actions that Kumry asks a person to confirm with multi-factor authentication stay in the app. If you are planning an integration that writes to Kumry, tell us what it needs to do and we will point you at the right endpoints.
Keys never reach /auth, /billing or administration paths.
API access is available on request
Organisation owners and admins create API keys and webhooks under Settings → Integrations. If you are building an integration and want to talk it through first, get in touch.