List an invoice's lines
GEThttps://
Returns one sales invoice's lines in their printed order, sort_order ascending.
Access
- Token scope
- api:
read: sales_invoices Without it:
403 insufficient-token-scope. - Permission
- sales_invoices::
read Without it:
403 insufficient-permission. - Feature
- Needs the billing feature on your organisation.
Without it:
404 endpoint-not-found. - Rate cost
- 1 unit, read bucket.
view=detailmakes it 3. Adds: each include +1,q+2. - Also
If-None-Matchanswers304when nothing changed. Never cached:private, no-store. Unknown query parameters are refused, never ignored.
Both are checked, scope first. A token never does more than its user. How access is checked
There is no organisation-wide collection of invoice lines: a line only means anything under the invoice it belongs to, so this nested path is the only way to list them and filter[sales_invoice_id] does not exist. A deleted invoice answers 404 for the whole path unless trashed=with is passed, which also includes the invoice's deleted lines. Defaults to the summary view; pass include=sales_invoice to expand the invoice each line points at.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
21 parameters in 7 groups
Views
Pagination
Rows per page. At most 25 when include names a to-many relation; a larger value is 400 invalid-query-parameter.
Default: 25
Opt in to page-number paging: 1-based, at most 1000. Omit it, the default, to page by opaque cursor, which is what links.next hands you. Cannot be combined with cursor. Published only on collections that count their rows on every request. This collection's default sort is a display position that changes whenever someone drags the list into a new order in plnnrly, so a page number can skip or repeat a row if the list is reordered between two page requests. These collections rarely exceed one page; for a stable walk, send sort=id and follow links.next without page.
Filters
- =
- equals
- [in]
- any of a comma-separated list
- [null]
trueorfalse: whether it is empty- [gte][lt]
- at least, less than
Project budget this invoice line settles.
A comma-separated list of at most 100 values.
Creation timestamp. Pair with sort=id for a stable full export.
Whether the line carries one aggregated price rather than hours times an hourly rate.
Subscription line this invoice line was generated from.
A comma-separated list of at most 100 values.
Search
Sorting
| Key | Sorts by |
|---|---|
sort_order | Position of the line within its invoice, first to last. |
name | Line label, A→Z. |
id | Id, ascending. An id never changes, so use this for a stable full export. |
updated_at | Last-write timestamp; pair with the id tiebreaker for sync. |
Prefix a key with - for descending.
Includes
| Path | Adds | Cost |
|---|---|---|
sales_invoice | The invoice this line belongs to. | +1 |
Other
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.
Response 200
Returns a page of SalesInvoiceRowList rows.
The rows, each a SalesInvoiceRowList.
per_page, next_cursor, prev_cursor, total, current_page, last_page.
self, next, prev.
Each row is a SalesInvoiceRowList: 24 fields.
Headers
ETag- A weak validator (
W/"…") of the rendered page. 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
8 errors every operation can return: 304, 400, 401, 404, 406, 429, 500, 503
304 Not modified.
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