API changelog release 26.05

Release 26.06 adds explicit archive and unarchive actions to the user endpoint and a new approvability filter to the draft logline list, reshapes the display label on matter contacts, and enforces the previously announced billing-address requirement for debtor contacts. Review the changes below to assess the impact on your integration.

Important changes

POST /api/v3/contacts/ and PUT /api/v3/contacts/{id}/ require default_billing_address for debtors: Creating or updating a debtor contact without a default_billing_address returns HTTP 400. Supply either a reference to an existing address or an inline address object on default_billing_address in the same request. This brings the API workflow in line with the UI workflow for creating a debtor and prevents synchronization errors with external software.

DELETE /api/v3/users/{id}/ is deprecated: This endpoint has always archived the user rather than deleting the record. Dedicated archive and unarchive actions (see New endpoints) now cover that behavior explicitly. DELETE remains functional for backward compatibility but is marked deprecated in the schema; migrate at your earliest convenience.

New endpoints

POST /api/v3/users/{id}/archive/ and POST /api/v3/users/{id}/unarchive/ archive and unarchive a user: Both actions return HTTP 204. Use archive in place of DELETE /api/v3/users/{id}/, and unarchive to restore an archived user.

Modified endpoints

GET /api/v3/mattercontacts/ returns a formatted display_name: The display_name field on a matter contact resolves to a label of the form matter / contact / [person] / kind. The field name and type (string) are unchanged.

PUT /api/v3/mattercontacts/{id}/ accepts the current kind when that contact kind is inactive: Updating a matter contact succeeds when its existing kind references a deactivated contact kind, provided the kind is unchanged. Selecting a different inactive kind is still rejected with HTTP 400. Already backported to release 26.05; customers on the latest patch have the fix.

GET /api/v3/draftloglines/ accepts an approvable_by_me filter: The list endpoint accepts an optional approvable_by_me boolean query parameter that restricts results to draft loglines the authenticated user can approve. For example, GET /api/v3/draftloglines/?approvable_by_me=true returns only the loglines awaiting the authenticated user's approval.

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