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

# Consignado API and streaming contracts

> Documentation now covers the Consignado client API and guide, plus current streaming catalog, routing, and delivery contracts.

<Badge stroke icon="calendar-days" iconType="regular">August 23, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams that integrate with the Consignado API, consume Midaz or Consignado events, or operate Fetcher terminal-event delivery.

## What changed

***

The Consignado reference now covers 55 client-facing operations, including setup, margin, auctions, registration, servicing, portability, guarantees, reconciliation, operations, and configuration guidance.

Midaz's `GET /v1/streaming/manifest` describes its public JSON business-event catalog and topic mapping. The former internal `billing_recorded` Protobuf stream has been retired and is not a separate route in the current runtime.

`consignado.portability_proposal.received` is operational. The scheduled portability-discovery poller emits it when it finds a live M011 offer and records its durable marker with the streaming outbox envelope.

Fetcher persists terminal state with a pending marker before its separate durable-outbox insert. Its repair loop re-emits the same `ce-id` until that marker clears. Consumers must continue to deduplicate CloudEvents by `(ce-source, ce-id)`.

SPI consumers derive v3 subscriptions from the producing application stream rather than per-event topic overrides. Bank Transfer uses one v3 application topic and its documented CloudEvents source constraint. SISBAJUD guarantees the tenant header for single-tenant `block_account.created` emissions only.

This is a documentation correction of implemented contracts. It does not announce a runtime release.

## Impact

***

**Classification: Review recommended.** The update adds API and guide coverage and clarifies the public catalog boundary and delivery behavior. Teams using the affected API or streams should confirm their routing, catalog assumptions, and idempotency handling.

## What you need to do

***

<Steps>
  <Step>Review the Consignado API reference and guide before implementing or changing an integration.</Step>
  <Step>Use the Midaz streaming manifest for the current public JSON business events. Do not infer a separate `billing_recorded` stream.</Step>
  <Step>If you consume Consignado events, handle `consignado.portability_proposal.received` as an operational event.</Step>
  <Step>Keep Fetcher consumers idempotent and deduplicate CloudEvents by `(ce-source, ce-id)`.</Step>
</Steps>

### Deadline

Review before the next Consignado, streaming-consumer, or Fetcher deployment.

## Resources

***

* [Event streaming overview](/en/reference/events/overview)
* [Midaz events](/en/reference/events/midaz)
* [Consignado events](/en/reference/events/consignado)