Sign in

v1

latestOpenAPI 3.0.32026-07-242644125.9 KB
Verifications

Create Verification

Initiates a new verification process. Use an 18-char CURP for individuals or a 12-char RFC for businesses.

post/verifications

Request body

identifierstring required

Identifier to verify. Use an 18-char CURP for individuals or a 12-char RFC for businesses.

external_idstring

Optional external identifier for tracking purposes. Can be used to correlate this verification with your internal systems.

rfcstring

Optional. If the user's RFC is provided, BDI uses it directly to retrieve invoice data, increasing the probability of recovering data for this individual.

phonestring

Optional. Helps increase the probability of recovering data for this individual.

emailstring email

Optional. Helps increase the probability of recovering data for this individual.

Example request

{
  "identifier": "CUAI911021MOCRQS09",
  "external_id": "USER_67890_VERIFICATION_001",
  "rfc": "ABCD123456XYZ",
  "phone": "+525512345678",
  "email": "user@example.com"
}

Response

Verification process initiated successfully. The process is asynchronous. A webhook will be sent upon completion. The response includes the verification ID and initial status, along with the consent_id that was automatically found.

idstring uuid

Unique identifier for the verification process.

identifierstring

The identifier for which the verification was initiated.

status'in_progress'

The initial status of the verification.

consent_idstring uuid

The ID of the consent that was found and used for this verification.

created_atstring date-time

Timestamp of when the verification was created.

external_idstring nullable

The external identifier provided in the request, if any.