Add a line to an invoice
POSThttps://
Creates one line on the invoice named in the path and returns it in the detail view, with a Location header pointing at the flat item path.
Access
- Token scope
- api:
write: sales_invoices Without it:
403 insufficient-token-scope. - Permission
- sales_invoices::
create Without it:
403 insufficient-permission. - Feature
- Needs the billing feature on your organisation.
Without it:
404 endpoint-not-found. - Rate cost
- 1 unit, write bucket. A write costs the same whatever
viewyou ask for. - Also
- Accepts
Idempotency-Key. Never cached:private, no-store. Unknown body keys are refused, never dropped.
Both are checked, scope first. A token never does more than its user. How access is checked
The invoice comes from the path, so sales_invoice_id is not accepted in the body and a line can never be moved between invoices. vat_rate defaults to the organisation's configured VAT percentage. vat_amount and total_amount are server-assigned, always computed from quantity, unit_price and vat_rate; total_amount excludes VAT. The invoice's own subtotal, vat_total and total are recalculated from all of its lines in the same transaction. A deleted invoice answers 404, and a legacy or synced invoice answers 409 state-conflict. A caller without sales_invoices::finalize also returns the invoice to pending_approval, as editing the invoice itself does. exact_item_id is optional here as it is in plnnrly, but in an organisation using Exact a line without it fails the whole invoice's sync, and naming an exact_item_id does not auto-fill the VAT code, GL account or hourly rate plnnrly would fill in from it.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
Request headers
A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
Request body
Unknown keys are refused with 422, naming the key.
The line label, as printed on the invoice. Exact Online prints this when description is empty.
Number of units billed. Fractional and signed: a budget row carries hours, and a credit line carries a negative quantity.
2 decimal places, may be negative
At least -99999999.99. At most 99999999.99.
Price per unit, excluding VAT. This is what actually bills.
2 decimal places, may be negative
At least -99999999.99. At most 99999999.99.
Rate plnnrly recomputes unit_price from when the aggregated-price toggle is switched on a budget row. Stored exactly as sent and null when omitted; it feeds no server-side computation.
2 decimal places, may be negative
True: one line of quantity 1 priced at hours times rate. False: quantity carries the hours and unit_price the hourly rate.
Project budget this invoice line settles, when the row was generated from budget hours.
Subscription line this invoice line was generated from, when the row came out of a subscription renewal rather than being typed by hand.
Exact Online article identifier this line bills against. Empty is accepted, but a row without it fails the whole invoice's Exact sync.
Response 201
Returns a SalesInvoiceRow in the detail view.
Headers
ETag- A strong validator of exactly this representation.
Idempotency-Replayedtruewhen this response was replayed from a storedIdempotency-Keyrather than produced by a new write.Location- The absolute URL of the created or queued resource.
RateLimit- The IETF
httpapi-ratelimit-headersform of your remaining allowance on the tightest bucket this request touched. RateLimit-Policy- The ceiling and window of that bucket, as
<limit>;w=<seconds>. X-Request-Id- The server-generated ULID correlating this response with our logs.
Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning
The invoice this line belongs to. Taken from the path on create and never writable afterwards: a line cannot be moved to another invoice.
The invoice this line belongs to.
Subscription line this invoice line was generated from, when the row came out of a subscription renewal rather than being typed by hand.
Project budget this invoice line settles, when the row was generated from budget hours.
Exact Online article identifier this line bills against. Empty is accepted, but a row without it fails the whole invoice's Exact sync.
The line label, as printed on the invoice. Exact Online prints this when description is empty.
Number of units billed. Fractional and signed: a budget row carries hours, and a credit line carries a negative quantity.
2 decimal places, may be negative
Price per unit, excluding VAT. This is what actually bills.
2 decimal places, may be negative
Rate plnnrly recomputes unit_price from when the aggregated-price toggle is switched on a budget row. Stored exactly as sent and null when omitted; it feeds no server-side computation.
2 decimal places, may be negative
True: one line of quantity 1 priced at hours times rate. False: quantity carries the hours and unit_price the hourly rate.
VAT on this line: quantity times unit_price times vat_rate, rounded to two decimals. Recomputed by the server whenever one of those three changes.
2 decimal places, may be negative
Line total excluding VAT (quantity times unit_price), which is the convention the invoice form writes. Recomputed by the server whenever quantity or unit_price changes.
2 decimal places, may be negative
Position of the line within its invoice, and the default sort key. Assigned on create; there is no way to reorder lines through the API.
Errors
415 Unsupported media type.
422 Unprocessable content.
7 errors every operation can return: 400, 401, 404, 406, 429, 500, 503
400 Bad request.
idempotency-key-requiredinvalid-cursorinvalid-query-parametermalformed-requestunsupported-parameter
401 Unauthenticated.
404 Not found.
406 Not acceptable.
429 Too many requests.
500 Server error.
503 Service unavailable.
This path allows GET, POST. Anything else answers 405.
Something wrong or missing on this page? Tell us