API changelog release 26.07 (July)

Release 26.07 adds filters and read-only fields for the billing, user, and contact endpoints, and lets the invoiceline object_type filter match several types in one query. Review the changes below to assess the impact on your integration.

Important changes

GET /api/v3/invoicelines/ filter object_type interprets comma-separated values: The object_type query parameter changed from an exact-match filter to a multi-value in filter. A single value such as ?object_type=logline behaves as before; a value containing a comma is split into an OR list rather than matched literally, so several types can be passed at once, for example ?object_type=logline,expense. The object_type filter on GET /api/v3/custominvoicelines/ behaves the same way.

POST /api/v3/loglines/ and PUT /api/v3/loglines/{id}/ reject time entries on blocked submatters: Writing or updating a logline whose submatter has time entry blocked returns HTTP 400, with the error keyed on the submatter field. This matches the validation applied in the web interface, and the same check covers POST /api/v3/draftloglines/.

Modified endpoints

/api/v3/invoices/ gains a loglines field and an is_credit_invoice filter: The invoice representation includes a read-only loglines field that hyperlinks to the invoice's effective loglines. The list endpoint accepts an is_credit_invoice boolean filter, for example GET /api/v3/invoices/?is_credit_invoice=true.

GET /api/v3/invoicelines/ exposes per-line breakdown fields: Partial-payment invoicelines include a read-only partial_lines field listing the source invoicelines each partial-payment line was split from. Logline invoicelines include a read-only amounts_distribution field, an object keyed by user that maps each contributing user to the ex-tax amount attributed to them, with a null key carrying the amount not attributed to any user.

GET /api/v3/custominvoicelines/ accepts a custom_ledger_account filter: The list endpoint accepts a custom_ledger_account query parameter to return only the custom invoicelines posted to that ledger account.

GET /api/v3/chargeables/ exposes amount_in_invoice_currency: The chargeable representation includes a read-only, nullable amount_in_invoice_currency field carrying the amount converted into the invoice currency. The field returns null when no conversion applies.

GET /api/v3/contacts/ returns a contacts relation: Both the list and detail representations include a read-only contacts field, a hyperlinked collection of the contacts related to a given contact. For example, contact persons linked to an organization-type Contact instance.

/api/v3/users/ exposes modified_date and adds modified-date, selectability, and time-writer filters: The user representation includes a read-only modified_date field. The list endpoint accepts modified_date__gte and modified_date__lte range filters, letting an integration fetch only the users changed since its last sync, plus is_selectable and is_timewriter boolean filters.

GET /api/v3/mattercontacts/ accepts a kind filter: The list endpoint accepts a kind query parameter to filter matter contacts by contact kind, passed as the contact kind's id. Combine it with the matter filter to retrieve only the contacts of a given kind for a matter, for example ?matter={id}&kind={id}, instead of fetching every matter contact and filtering client-side.

GET /api/v3/firms/ exposes bankgiro and plusgiro fields: The firm representation includes read-only bankgiro and plusgiro fields for use as Peppol UBL payment means. These fields are present only for tenants with the Swedish giro Peppol feature enabled.

For more information about Legalsense features, please visit our knowledge base.