Credit Risk / API
Added the lien continuations endpoint to the reference
Accounts that file UCC liens through Middesk can extend a lien before it lapses with POST /v1/liens/{lien_id}/continuations. The endpoint returns 201 with the new continuation, including status, old_lapse_date, new_lapse_date, and filing details once available. If a continuation is already in flight for the lien, the request returns that continuation with 200 instead of creating a duplicate, so retries are safe. packet_number is optional and is generated when omitted; it cannot contain underscores unless the lien being continued already has an underscored packet number, and a lien that is not eligible for continuation returns 422. View the lien continuation reference.
Entity Management / API
Added pagination and an external_id filter to listing registration requests
GET /v1/partner/registration_requests supports pagination when you supply both page and per_page. Paginated responses are ordered by creation time, then ID, and include has_more and total_count. Supplying only one of the two parameters, or neither, keeps the existing behavior of returning every registration request, so no action is required. Pass external_id to return only registration requests for the company with that exact external ID. View the list registration requests reference.
Agents / Webhooks
Added agent application records and screenshot status to custom webhook payloads
Custom event schemas for business.updated can select agent_applications, a record of what an agent found, how each finding was applied to the Business report, and which review tasks changed as a result. When web evidence screenshot capture is enabled, the nested screenshot_captures field shows whether captures for that run are still pending; settled_at is null while any capture is pending and holds a timestamp once all capture attempts finish. If screenshots are still pending when an agent finishes, Middesk sends another business.updated event after capture completes, so screenshot-dependent workflows such as retrieving the latest Business PDF can wait for that signal. Default webhook payloads are unchanged. View the review work guide.
Agent run streams return 204 for settled runs
GET /v1/runs/{id}/stream returns 204 No Content without opening a stream when the run is already completed, interrupted, or errored. Running runs continue to stream events. Clients that reconnect to a stream should treat 204 as a signal that the run has settled and retrieve its final state instead of retrying. View the stream agent run events reference.