Declare an indirect participant the tenant settles
Declares an indirect participant (ispb) that the tenant settles for, in force from validFrom, with no end until you end it with the end route. The id of the response addresses the declaration from then on.
A close classifies each settlement outside SPI by the declarations in force at its cutoff. When both ISPBs are the tenant’s, the settlement is transactionDetail 6. When one ISPB is the tenant’s or the one of a declared indirect participant, for the civil day of settledAt, it is transactionDetail 5. Any other pair stays out of the rows.
The tenant’s own ISPB (body.ispb), or a validity that overlaps another declaration of the same ISPB (body.validFrom), answers 422 (PIX-0719). The message of an overlap names the id of the declaration it meets. A declaration that starts after the last day of an earlier one, or of one voided, is accepted.
The optional clientRequestId keys the declaration per tenant. The same body under it answers the current declaration and creates nothing. Another body under it answers 409 (PIX-0717). A declaration, an end or a void that covers a closed month leaves that month’s report unchanged. It enters only the close that follows a reopen.
Headers
REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. An identical resend within 1 hour returns the original response, status included, with X-Idempotency-Replayed: true. Reusing the key with a divergent method, URL or body is PIX-0031 @ 412.
1 - 64Body
Response
Created

