> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# List failed orders (admin)

> Lists the resolved institution's judicial orders in the FAILED terminal state, with offset pagination. Items are summary fields only; full decrypted detail is the get-order endpoint.



## OpenAPI

````yaml en/openapi/v3-current/sisbajud.yaml get /v1/admin/failed-orders
openapi: 3.0.3
info:
  title: Lerian SISBAJUD API
  description: >-
    API for Lerian SISBAJUD — the participant-side rail that integrates the
    institution with Banco Central do Brasil's SISBAJUD (Sistema de Busca de
    Ativos do Poder Judiciário) system for judicial asset blocking and
    unblocking. It covers judicial-order administration, remittance and return
    file management, reconciliation, SLA monitoring, LGPD data-subject requests,
    and per-institution configuration and connector credentials.
  version: v1.0.0
servers:
  - url: https://sisbajud.sandbox.lerian.net
security: []
tags:
  - name: Admin
    description: >-
      Administrative operations over judicial orders: listing and detail,
      failed-order reprocessing, remittance and return file access,
      reconciliation runs and status, SLA-risk monitoring, processing
      statistics, audit-trail verification, cross-organization subject
      summaries, and LGPD data-subject requests and justifications.
  - name: Institution
    description: >-
      Per-institution configuration and connector credentials: configuration
      upsert with tokenization-keyset provisioning, safe configuration read, and
      outbound connector credential registration and rotation.
paths:
  /v1/admin/failed-orders:
    get:
      tags:
        - Admin
      summary: List failed orders (admin)
      description: >-
        Lists the resolved institution's judicial orders in the FAILED terminal
        state, with offset pagination. Items are summary fields only; full
        decrypted detail is the get-order endpoint.
      parameters:
        - description: Page size (coerced into [1, 200]; default 20)
          in: query
          name: limit
          schema:
            type: integer
        - description: Row offset (coerced to >= 0; default 0)
          in: query
          name: offset
          schema:
            type: integer
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminOrderPage'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
        '503':
          description: Service Unavailable
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.AdminErrorResponse'
components:
  schemas:
    http.AdminOrderPage:
      properties:
        data:
          items: {}
          type: array
        limit:
          type: integer
        offset:
          type: integer
        total:
          type: integer
      type: object
    http.AdminErrorResponse:
      properties:
        code:
          type: string
        details:
          additionalProperties: {}
          type: object
        message:
          type: string
        title:
          type: string
      type: object

````