DEVELOPER API
Cove in your own code — through a REST API and MCP.
A REST API at /api/v1, described with OpenAPI 3.1. Issue invoices, download the files for НАП, sync the general ledger and match bank statements — from your code.
- OpenAPI 3.1 and interactive docs
- Scoped keys for every integration
- Signed webhooks and an MCP server
Everything you need. In one workflow.
Invoicing
Issue invoices, proformas and notes, email them and mark them paid.
Purchases, expenses and revenue
File received invoices and receipts, expenses and revenue — with the document's file.
Clients, CRM and catalogue
Clients and addresses, sales opportunities, products, price lists, stock and orders.
Staff
Employees, payroll records, leave and leave requests — and the Д1 and Д6 returns for НАП.
Bulk import and export
Up to 2,000 rows per request, and export to CSV, Excel, TXT, JSON or PDF.
Signed webhooks
Events for records created, changed and deleted, signed with HMAC-SHA256 and retried.
VAT, ready for НАП
The VAT return and the files for НАП, period locks and the coefficient under чл. 73, ал. 5 ЗДДС.
Accounting
Chart of accounts, entries and reversals, the trial balance, financial statements, SAF-T and the ГДД under чл. 92 ЗКПО.
Bank statements
Import statements and match their transactions to invoices through the API.
The same rules as the dashboard.
Every request runs as the member who owns the key — with the same rights, plan limits and locked periods as in the dashboard. A key sees only its own company's data.
SECURITY
Every key scoped, every change in the audit log
Keys are created, rotated and revoked in Developers. What each key reaches is set explicitly — and every change it makes stays in the team's audit log.
39 read and write scopes
And never more than the role of the member who owns the key.
Rate limits
120 a minute per key by default, with X-RateLimit headers, and 429 with Retry-After when exceeded.
Expiry and last use
A key can expire after 30, 90 or 365 days, and for each you see when it was last used.
Clear steps. Connected data.
- Step 1
Create a key
In Developers, choose the key's scopes and expiry.
- Step 2
Call the API
With a Bearer header — or try every endpoint in the docs at /api/v1/docs.
- Step 3
Subscribe to events
Add an HTTPS address for webhooks and verify the signature on every delivery.