Create delivery note
Create a delivery note with its received lines for the organisation. Delivery notes are trusted platform data and do not require approval.
Authentication. An API key (x-dolfin-api-key) together with the x-dolfin-organisation-id header identifying the organisation, or a JWT Bearer token that carries the organisation in its claims.
Authorizations
An API key issued to your client. It carries the client's scope; org-scoped calls also require the x-dolfin-organisation-id header. Keys are created and revoked by a client administrator.
Headers
Target organisation. Required when authenticating with an API key; omit for Bearer callers (resolved from the token).
Body
Creates a delivery note with its received lines.
Supplier the goods were received from. Optional — may be assigned later.
Caller's own reference for the note (a reverse pointer to the platform's record). Optional.
Human delivery-note number. Required.
Loose header link to a purchase order. Optional.
When the goods were received. Optional.
The received lines. At least one is required.
Response
Created
A delivery note and its received lines.
Human delivery-note number. Required and unique within the organisation.
Unique identifier of the delivery note.
The organisation that owns the delivery note.
The supplier the goods were received from, if assigned.
Caller's own reference for the note (a reverse pointer to the platform's record), if any.
Loose header link to a purchase order, if one was provided. Optional.
When the goods were received, if recorded.
Lifecycle status: Draft, Open, PartiallyMatched, FullyMatched (all derived from matching), or the manual terminal states Closed / Cancelled.
Draft, Open, PartiallyMatched, FullyMatched, Closed, Cancelled The received lines, in display order.
When the delivery note was created.
When the delivery note was last updated.