Sales Delivery Notes

Create, read, update and delete customer sales delivery notes (albaranes de entrega)

📄️ Get sales delivery note by ID

Returns a single customer sales delivery note by its primary key, including line items and payments. Listing (`GET` without id) returns headers only. The response carries a strong `ETag` header with the current version.

📄️ Update sales delivery note

Full replacement of an existing customer sales delivery note. Send the `If-Match` header with the current ETag for optimistic concurrency control.

📄️ Delete sales delivery note

Deletes a customer sales delivery note. Send the `If-Match` header with the current ETag for optimistic concurrency control.

📄️ Merge-patch sales delivery note

RFC 7396 merge-patch over `application/merge-patch+json`. Send only the fields you want to change; include a field with value `null` to remove it. Use the `If-Match` header for optimistic concurrency control.

📄️ List sales delivery notes

Returns a paginated list of customer sales delivery notes with envelope `{data, totalCount, skip, limit, hasMore}`. Supports optional RSQL `filter`, `sort` (default `lastModifiedAt:desc`), `skip`/`limit` pagination and `modifiedAfter`/`modifiedBefore` bookends. Limit is capped at 200; skip is clamped to >= 0.

📄️ Create sales delivery note

Creates a new customer sales delivery note with the provided data and optional line items and prepayments. Business logic runs in the legacy WAR via the internal commands gateway.