v1.1.0 — recipient and payment_info

What breaks

• PUT /v1/invoices/{invoice_id} schema change — recipient and payment_info now use allOf composition referencing Recipient and PaymentInfo schemas. The fields (nif, legal_name, iban, method, etc.) remain available but the schema path changed from inline properties to a $ref. Clients using generated SDKs may need to regenerate.
• SDK regeneration recommended — If you use generated clients from the OpenAPI spec, regenerate them to pick up the new schema references. The underlying fields are the same; only the structure (and how the SDK types represent them) has changed.

What else changed

• Structured recipient and payment_info — PUT /v1/invoices/{invoice_id} now uses allOf composition with PaymentInfo and Recipient schemas. Fields like nif, legal_name, iban, method are still available via the referenced schemas, but the structure changed from inline to composed. Regenerate your SDK if you use one.
• New series defaults endpoints — POST /v1/configuration/series/defaults and GET /v1/configuration/series/defaults-status allow setting and checking per-document-type default series.
• Idempotency-Key header — Now formally documented on POST /v1/customers.
• Invoice email options — All invoice endpoints now return email_config and send_automatically fields in responses.

Endpoints

• PUT/v1/invoices/{invoice_id}recipient and payment_info now use allOf composition — update your request payload structure
• POST/v1/configuration/series/defaultsSet default series per document type
• GET/v1/configuration/series/defaults-statusCheck which series have defaults configured

Where to go next