Renamed the active-company header
The request header that selects which company a request operates on has been renamed from X-Active-Profile to Beel-Active-Company.
The request header that selects which company a request operates on has been renamed from X-Active-Profile to Beel-Active-Company.
What else changed
- Send
Beel-Active-Company: <company_id>to scope a request to a specific company. - The previous
X-Active-Profileheader keeps working during a deprecation grace period, so you can migrate at your own pace. - While you still send the old header, responses include a
Deprecation: trueheader and aLink: …; rel="deprecation"pointing to this entry. Switch toBeel-Active-Companyto clear it.
Where to go next
API v1.3.0 — contract fixes: flexible idempotency keys, optional country, HTTPS-only webhooks
Contract-correctness wave from an API test pass. Idempotency keys no longer have to be UUIDs, address country becomes optional, webhook endpoints must be HTTPS, and several error responses are now more accurate (correct codes, correct status, and a previously-opaque 500 turned into an actionable 422).
API v1.2.0 — VeriFactu validation pack, public error catalog, metadata filters, RD-ley rates, BIZUM
Third wave of VeriFactu compliance hardening: invalid fiscal combinations are now rejected at request time with specific 422s, a public error-code catalog is available at docs.beel.es with stable per-code pages, Stripe-style metadata filtering on the invoices list, RD-ley 11/2022 temporary rates (5% IVA + 0.625% recargo de equivalencia), BIZUM as a new payment method, and several Stripe Connect refinements.