> ## 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. # Submit a batch of settlement operations (synchronous NDJSON) > Accepts newline-delimited JSON (application/x-ndjson); the NDJSON media type describes the request wire format only, not how operations are persisted. Each line is one operation, validated and created through the same pipeline as POST /v1/operations, grouped under one generated batchId. Processing is synchronous: the request is received in full and its line count validated before any operation is persisted. The line count is capped (a configured limit, default 50000); an over-limit batch is rejected atomically with 413 and no operations are persisted. Within an accepted batch, one bad line is rejected with a per-line error without aborting the batch. Optionally idempotent via the Idempotency-Key header. Errors are RFC 9457 problem+json. ## OpenAPI ````yaml en/openapi/v3-current/slc.yaml post /v1/operations/batch openapi: 3.1.0 info: description: >- API for Lerian SLC — the participant-side rail that connects the institution to Núclea's SLC deferred-net card settlement. It covers settlement-operation intake and lifecycle, clearing positions, the participant and arrangement registry, generated reports, embedded XSD schema introspection, transmission recovery and connectivity to Núclea, BYOK Model-A signing-key import, and tenant-scoped webhooks. title: Lerian SLC API version: 1.0.0 servers: - url: https://slc.sandbox.lerian.net security: - BearerAuth: [] tags: - description: >- Settlement operation lifecycle — create, list, query, and control the NUliquid-tracked card operations (NUliquid = the 21-position id Núclea assigns each accepted operation) through the state machine. name: Operations - description: >- Participant catalog — the acquirers, sub-acquirers, IF Domicílio (bank where the merchant receives its sales), and settlement FIs (financial institutions) that take part in card settlement. name: Participants - description: >- Card arrangements (bandeira/scheme configurations, e.g. Visa/Master/Elo) attached to a participant. name: Arrangements - description: >- Regulated transport orchestration to Núclea/SILOC (the private card clearing house that operates the SILOC settlement system) — dispatch, recovery, retransmission, and connectivity testing over managed file-transfer, message-broker, and REST. name: Connectivity - description: >- Multilateral netting clearing positions — the net amount each participant settles per STR cycle (STR = Banco Central reserves-transfer system). name: Clearing - description: >- SaaS BYOK (Bring Your Own Key) signing-key provisioning — import parameters and register the client's ICP-Brasil A1 (Brazilian PKI server certificate, 1-year validity) certificate material used to sign ASLC files; the private key never leaves the client's HSM/KMS/Vault. name: SigningKey - description: >- ASLC file intake and status — passthrough submission and processing status of the official Núclea card-settlement XML files (ASLC = Arquivo do Sistema de Liquidação de Cartões). name: Files - description: >- Read-only introspection of the embedded Núclea ASLC/RSFN (National Financial System Network) XSD schemas used to validate outbound and inbound messages. name: XSD Schemas - description: Read-only regulatory, compliance, and operational settlement reports. name: Reports - description: >- Outbound business-event webhook subscriptions and delivery management for consumers (Midaz, client ledgers, Cabine — all optional). name: Webhooks - description: >- Administrative operations — hot-reloadable runtime configuration, dead-letter-queue inspection/replay, and outbox redispatch. name: Admin paths: /v1/operations/batch: post: tags: - Operations summary: Submit a batch of settlement operations (synchronous NDJSON) description: >- Accepts newline-delimited JSON (application/x-ndjson); the NDJSON media type describes the request wire format only, not how operations are persisted. Each line is one operation, validated and created through the same pipeline as POST /v1/operations, grouped under one generated batchId. Processing is synchronous: the request is received in full and its line count validated before any operation is persisted. The line count is capped (a configured limit, default 50000); an over-limit batch is rejected atomically with 413 and no operations are persisted. Within an accepted batch, one bad line is rejected with a per-line error without aborting the batch. Optionally idempotent via the Idempotency-Key header. Errors are RFC 9457 problem+json. operationId: createOperationsBatch parameters: - description: Idempotency key for safe retries of the whole batch. in: header name: Idempotency-Key schema: type: string requestBody: content: application/x-ndjson: schema: type: string description: >- Newline-delimited JSON operations (application/x-ndjson); one CreateOperationRequest per line. required: true responses: '202': content: application/json: schema: additionalProperties: false properties: accepted: description: Count of accepted operations. examples: - 48 format: int64 type: integer batchId: description: Generated batch id grouping every line of the submission. examples: - 018f8a3e-4b2c-7c1a-9e5d-2f6a1b3c4d5e type: string errors: description: >- Per-line rejection errors (capped at the first batchErrorCap entries). items: $ref: '#/components/schemas/BatchError' type: - array - 'null' errorsTruncated: description: >- True when more rejections occurred than the errors array lists. examples: - true type: boolean meta: $ref: '#/components/schemas/BatchMeta' description: Batch response envelope metadata (requestId + timestamp). rejected: description: Count of rejected lines. examples: - 2 format: int64 type: integer required: - batchId - accepted - rejected - errors - errorsTruncated - meta type: object description: >- Batch accepted; per-line accepted/rejected counts and errors with the meta envelope. '400': content: application/problem+json: schema: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: >- A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object description: Malformed batch request. '401': content: application/problem+json: schema: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: >- A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object description: Authentication required. '403': content: application/problem+json: schema: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: >- A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object description: Forbidden (operations:write scope required). '413': content: application/problem+json: schema: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: >- A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object description: Batch exceeds the maximum number of lines. '500': content: application/problem+json: schema: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: >- A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object description: Internal error (scrubbed). security: - BearerAuth: [] components: schemas: BatchError: additionalProperties: false properties: code: description: Coded error identifier for the rejection. examples: - SLC-0104 type: string details: additionalProperties: {} description: >- Structured context for the rejection (e.g. the existing operationId of a duplicate). type: object externalId: description: >- Best-effort external id of the rejected line (empty when the line could not be parsed that far). examples: - acq-ext-2026-06-0002 type: string line: description: 1-based source line number of the rejected NDJSON line. examples: - 42 format: int64 type: integer message: description: Static, controlled human-readable rejection message. examples: - external id already used by another operation type: string required: - line - externalId - code - message type: object BatchMeta: additionalProperties: false properties: requestId: description: Client request id echoed back from the X-Request-Id header. examples: - req-2026-06-15-abc123 type: string timestamp: description: Response generation timestamp (RFC3339). examples: - '2026-06-15T10:50:00Z' type: string required: - requestId - timestamp type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````