List the tenant's averbação operations
Walks the tenant’s own averbação operation book, oldest claim first.
It answers from a LOCAL table and never reaches the Dataprev rail, so it cannot answer 501 and it is served even on a deployment where averbação itself is switched off. That deployment simply has an empty book. Distinguishing “nothing is stuck” from “the convergence loop is off” is what GET /v1/consignado/capabilities is for: read the averbacao_recovery family there, not the status of this response.
The tenant is derived from the validated identity and is never read from the request. There is no tenant parameter on this operation.
Paging is keyset over the operation’s own claim instant, which the table holds immutable by trigger, so a row’s position never moves and a page can neither skip nor repeat. Send the previous page’s page.next_after as after. has_more is true exactly when another page exists, and next_after is null exactly when it is false, so a client loop may terminate on either. The cursor never expires; a cursor this service did not mint is refused with 422 rather than silently restarting the scan from the top.
status may be repeated to narrow the page to several situations at once (status=averbacao_unknown&status=attachment_unknown). Omitting it means ALL eight situations, never none.
Authorizations
JWT bearer token issued by the identity provider.
Query Parameters
Narrows the page to the named situations. Repeat the parameter for several. Omitted means all eight.
claimed, averbacao_invoking, averbacao_unknown, attachment_pending, attachment_invoking, attachment_unknown, confirmed, rejected The previous page's page.next_after. Omitted starts at the oldest claim. A cursor this service did not mint is refused, never restarted from the top.
Maximum number of operations to return. Omitted means the ceiling of 200.
1 <= x <= 200
