Sign in

v1

latestOpenAPI 3.0.32026-07-242644125.9 KB
Verifications

Create Bulk Verifications

Initiates a new bulk verification process for a list of identifiers. Each item must be an 18-char CURP (individual) or a 12-char RFC (business). Each item requires a pre-existing consent, which is automatically discovered. The entire bulk request will be rejected if the payload structure is invalid or if any individual item is malformed (e.g., missing identifier). Failures of individual verifications during asynchronous processing (e.g., consent not found for an item, identifier not found by external systems) will be reflected in the status of those individual verifications.

post/verifications/bulk

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

Accepted. Batch verification creation queued successfully. Use the returned id to poll status via GET /verifications/bulk/{bulk_id}.

idstring uuid

Unique identifier for the bulk verification job. Use this to poll status via GET /verifications/bulk/{bulk_id}.

status'pending'

Status of the batch job. Returns 'pending' when queued.

total_itemsinteger

Total number of items in the batch request.

messagestring

Human-readable confirmation message.