REST API
OpenAPI/Swagger and an x-api-key. Create clients, products, quotes, delivery notes and invoices, record payments and download PDF and Facturae files.
Integrations
A documented REST API, accounting export to A3 and Dimoni, Facturae for public administrations and CSV import. No connectors that don't exist.
OpenAPI/Swagger and an x-api-key. Create clients, products, quotes, delivery notes and invoices, record payments and download PDF and Facturae files.
Assign 6 to 8 digit ledger accounts per category or client and download a ZIP for a date range to import into A3 or Dimoni.
Facturae 3.2.1 signed with the client's certificate and ready for FACe, with DIR3 codes.
Load clients and products from a spreadsheet when you start.
Invoices are immutable through the API: you can create, read and record payments, but not edit them. To correct, issue a corrective invoice.
| Resource | Operations |
|---|---|
| Invoices | List, create, record payments, PDF, Facturae, send and payment reminder |
| Corrective invoices | List |
| Recurring invoices | List, read, create, edit and delete |
| Quotes | List, create, edit, delete, PDF and send |
| Delivery notes | List, create, edit, delete, PDF and send |
| Clients | List, read, create and delete |
| Products | List, create and delete |
| Categories | List, create and delete |
| Expenses (supplier invoices) | List and read |
| Payment methods | List |
| Invoice types | List |
| OpenAPI specification | Download the JSON |
There are no native connectors. Integration with any ERP or CRM is done through the REST API, usually with a small piece of development on your side or ours.
It exports to A3 and Dimoni as a ZIP for a date range, using the ledger accounts you configure per category or client.
With a key sent in the x-api-key header. The key is created from the dashboard of each installation.
No. To detect changes you need to query the API.
In 30 minutes we go through your companies, your series and your VeriFactu setup. No commitment.