Verify a CID set against BACEN
Sends the participant’s sync verifier (the XOR of its active CIDs of one key type) to BACEN’s createSyncVerification and returns BACEN’s OK/NOK verdict verbatim. NOK means the CID sets diverge; resolve it with the CID set file and GET cids/entries/. The participant comes from X-ISPB.
Autorizações
JWT bearer token issued by the identity provider.
Cabeçalhos
Required key used to prevent replaying the mutation.
ISPB of the participant the call acts for. It must be this deployment's direct participant or an indirect it sponsors; the body never carries it.
^[0-9A-Z]{8}$"12345678"
Corpo
Key type whose CID set is verified.
CPF, CNPJ, EMAIL, PHONE, EVP "CPF"
The participant's own sync verifier: the XOR of every active CID of this key type, 64 hex characters.
^[0-9a-fA-F]{64}$"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
Resposta
Created
BACEN's own id for this sync verification.
"4521"
Key type that was verified.
"CPF"
ISPB the verification was run for, resolved from X-ISPB.
"12345678"
The sync verifier that was sent to BACEN.
"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
BACEN's verdict, verbatim: OK when the CID sets match, NOK when they diverge.
"NOK"
BACEN's operational envelope for this call; omitted when BACEN sent no correlation id.

