Purchase Delivery Notes

Create, read, update and delete supplier purchase delivery notes (albaranes recibidos)

📄️ Get purchase delivery note by ID

Returns a single purchase delivery note by its primary key, including line items and payments. Returns 404 when the requested ID belongs to a sales (issued) document.

📄️ Update purchase delivery note

Full replacement of an existing purchase delivery note. Send the `If-Match` header with the current ETag for optimistic concurrency control. The `issued` flag is forced to `false` server-side.

📄️ Delete purchase delivery note

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

📄️ Merge-patch purchase 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 purchase delivery notes

Returns a paginated list of supplier purchase 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. The constraint `issued==false` is always enforced server-side.

📄️ Create purchase delivery note

Creates a new supplier purchase delivery note with the provided data and optional line items and prepayments. The `issued` flag is forced to `false` server-side regardless of the request payload.