Trigger a sync verification
Starts a sync verification against BACEN. Send keyType to verify one scope and create a reconciliation job, or send an empty body ({}) to verify every scope that Pix Lerian already knows for your ISPB. Both modes answer 202 with the same {results: [...]} shape. In the all-scopes mode each scope resolves on its own to CREATED, ALREADY_ACTIVE, SKIPPED_RECENTLY_OK or FAILED, and a failure on one scope never stops the others.
A keyType outside the enum answers 400 (PIX-0003). In the single-scope mode the call answers 409 (PIX-0156) when an active job already exists for the scope, and 422 (PIX-0174) when Pix Lerian has not discovered the scope yet. The all-scopes mode reports the same two conditions per scope as ALREADY_ACTIVE and FAILED.
Authorizations
JWT bearer token issued by the identity provider.
Headers
REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. Resending the same key and request within 1 hour returns the original response, its status included, with X-Idempotency-Replayed: true. Reusing the key with a divergent method, path or body, or while the first request runs, is PIX-0031 @ 412.
1 - 64Body
Pix key type of the scope to verify; omit to fan out across every scope discovered for the tenant
"CPF"
Response
Accepted
Per-scope verification outcomes: exactly one element for an explicit-keyType request, one per scope discovered for the tenant when keyType was omitted (fan-out)

