> ## 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.

# Trigger a manual reconciliation (admin)

> Triggers a manual reconciliation run for the resolved institution and returns the run handle. scope selects the set (monitoring_orders default, all_pending, specific_order); orderId is required for specific_order and rejected (422) for any other scope. HTTP 200 means the run was CREATED and attempted synchronously — it does NOT mean reconciliation succeeded: a run can finalize FAILED (for example when the connector cannot be resolved) and still return 200 with ordersScheduled=0. Fetch the run status via GET /v1/admin/reconciliation to learn the terminal outcome. jobId is the run id; ordersScheduled is the number of orders this run reconciled. The institution is derived from the validated request identity, never from the payload.



## OpenAPI

````yaml en/openapi/v3-current/sisbajud.yaml post /v1/admin/reconciliation/trigger
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/reconciliation/trigger:
    post:
      tags:
        - Admin
      summary: Trigger a manual reconciliation (admin)
      description: >-
        Triggers a manual reconciliation run for the resolved institution and
        returns the run handle. scope selects the set (monitoring_orders
        default, all_pending, specific_order); orderId is required for
        specific_order and rejected (422) for any other scope. HTTP 200 means
        the run was CREATED and attempted synchronously — it does NOT mean
        reconciliation succeeded: a run can finalize FAILED (for example when
        the connector cannot be resolved) and still return 200 with
        ordersScheduled=0. Fetch the run status via GET /v1/admin/reconciliation
        to learn the terminal outcome. jobId is the run id; ordersScheduled is
        the number of orders this run reconciled. The institution is derived
        from the validated request identity, never from the payload.
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/http.TriggerReconciliationRequest'
        description: Reconciliation trigger options
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/http.TriggerReconciliationResponse'
        '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'
        '422':
          description: Unprocessable Entity
          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'
      security:
        - BearerAuth: []
components:
  schemas:
    http.TriggerReconciliationRequest:
      properties:
        orderId:
          format: uuid
          type: string
        organizationId:
          format: uuid
          type: string
        scope:
          enum:
            - monitoring_orders
            - all_pending
            - specific_order
          type: string
      type: object
    http.TriggerReconciliationResponse:
      properties:
        jobId:
          format: uuid
          type: string
        ordersScheduled:
          type: integer
        triggeredAt:
          type: string
      type: object
    http.AdminErrorResponse:
      properties:
        code:
          type: string
        details:
          additionalProperties: {}
          type: object
        message:
          type: string
        title:
          type: string
      type: object
  securitySchemes:
    BearerAuth:
      description: 'Bearer token authentication (format: "Bearer {token}")'
      in: header
      name: Authorization
      type: apiKey

````