Validate Key

Overview

This endpoint validates a Bre-B Key and optionally compares additional information such as participant, account, and owner details.

You can submit a Bre-B key (create by you or not) along with optional additional information. The API then returns a boolean‐style match response (e.g., MATCH / NO_MATCH) to indicate whether the key corresponds to the expected individual.

If the submitted information does not match the resolved owner of the key, you will not receive any PII of the correct owner. This enables validation without revealing confidential information.

Endpoint Behavior

  • The key object is required.
  • The objects participant, account, and owner are optional, when included, each will be checked independently.
  • Each field returns a match indicator (MATCH / NO_MATCH).
  • If the submitted key does not exist or is not ACTIVE, the API returns HTTP 404.

Endpoint Details

DefinitionDescription
Endpointhttps://api.paas.sandbox.co.passportfintech.com/v1/validate-key
MethodPOST
HeadersContent-Type: application/json, Authorization
AuthenticationAccess Token (Bearer Token)

Request Body

FieldTypeRequiredDescription
keyObjectYesKey to validate
key.key_typeStringYesKey type (e.g., PHONE BCODE, EMAIL, ID, or ALPHA)
key.key_valueStringYesKey value
participantObjectOptionalParticipant comparison data
participant.identification_numberStringOptionalParticipant NIT
participant.nameStringOptionalParticipant name
accountObjectOptionalAccount comparison data
account.account_typeStringOptionalAccount type (e.g., ORDINARY or LOW_VALUE)
account.account_numberStringOptionalAccount number
ownerObjectOptionalAccount owner information
owner.first_nameStringOptionalFirst name
owner.second_nameStringOptionalMiddle name
owner.first_last_nameStringOptionalSurname
owner.second_last_nameStringOptionalSecond surname
owner.typeStringOptionalOwner type (e.g., INDIVIDUALor BUSINESS)
owner.identification_typeStringOptionalID type (e.g., CC)
owner.identification_numberStringOptionalID number

Example Request

JSON
Copy

Response

  • HTTP Status Code: 200 OK.
  • The response will contain the validation details of the key.

Example of Response

JSON
Copy

Common Errors and Handling

HTTP Status CodeMeaningDescription
400 Bad RequestInvalid requestMalformed JSON or invalid fields
401 UnauthorizedMissing/expired tokenBearer token invalid or expired
403 ForbiddenNot allowedCaller not permitted to validate keys
404 Not FoundKey invalidKey does not exist or is not ACTIVE
500 Internal Server ErrorServer errorUnexpected system error

Best Practices

  • Always include the key object, all other fields are optional.
  • Use optional validation blocks (account, participant, owner) only if you need to verify related information.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard