API v1.0.1 — VeriFactu operation_date & spec improvements
This release aligns the API with Spanish anti-fraud law (Ley Antifraude / VeriFactu) requirements for invoice dates. The issue_date is now always set to today and a new operation_date field lets you record when the operation actually took place.
This release aligns the API with Spanish anti-fraud law (Ley Antifraude / VeriFactu) requirements for invoice dates. The issue_date is now always set to today and a new operation_date field lets you record when the operation actually took place.
What else changed
- New
operation_datefield on invoices — use when invoicing for a past operation (e.g., services delivered last month but invoiced this month) issue_dateis now read-only and always set to today per VeriFactu regulationsissue_dateremoved from required fields in CreateInvoiceRequest- Duplicate invoice no longer accepts a custom
issue_date— duplicates are always dated today - Idempotency header renamed from
X-Idempotency-KeytoIdempotency-Key(standard naming) - Improved
due_datedocumentation — must be same as or after today's date - New
start_datefield on recurring invoice creation
Endpoints
- POST/v1/invoicesoperation_date replaces issue_date in request body
- PUT/v1/invoices/{invoice_id}operation_date (nullable) replaces issue_date
- POST/v1/invoices/{invoice_id}/duplicateissue_date param removed from request
Where to go next
API v1.0.3 — VeriFactu exemptions, document types, stricter validations
Second round of VeriFactu compliance improvements: invoice lines can now carry an explicit exemption reason, the tax-types endpoint exposes the full LIVA exemption catalog, invoice series can be typed, and the `id_otro` VeriFactu rules are now enforced with specific error messages.
BeeL. API v1.0 — Public Launch
The BeeL. API is now publicly available. Full REST API for invoicing, customer management, products, tax configuration, and VeriFactu compliance — all with a 7-day free trial.