Get an indirect participant
Returns one indirect participant by id with its full registry record: lifecycle status, the derived @pi_{ispb} settlement-account alias its money moves through, the delivery configuration, the own-QR-certificate configuration, and provisioning.failedStep when a provisioning step failed. Call it to confirm an indirect reached ACTIVE after a registration or a provisioning retry, and to read back the @pi alias.
Read-only, and uncached: it always reads the registry row, unlike the cached slim projection the money paths resolve against — so this is the operation that tells you the CURRENT state, while a suspend may take up to the resolution-cache TTL to be seen by every replica. delivery.secret always comes back as ”***”: the stored credential is write-only and no operation returns it, so a lost secret is replaced with a PATCH rather than recovered.
Refusals: 404 PIX-0095 when no indirect with that id exists in this tenant — an id belonging to another tenant is deliberately indistinguishable from an unknown one; 422 PIX-0098 when indirectId is not a valid UUID.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
The indirect participant id.
"018f2b7c-0000-7000-8000-000000000000"
Response
OK
Creation timestamp (UTC).
Delivery endpoint (secret redacted).
The indirect participant id (routing identifier).
"018f2b7c-0000-7000-8000-000000000000"
The indirect PSP's ISPB.
"12345678"
Delivery mode.
"raw"
Display name.
"Indirect PSP Ltda"
The derived @pi_{ispb} Midaz account alias.
"@pi_12345678"
Provisioning-saga state.
Own-QR-code certificate configuration.
Lifecycle status.
"ACTIVE"
Last-update timestamp (UTC).

