Verifications

Create Bulk Verifications

Changed on

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). Send ip_address in each item to record that item's consent under your company's privacy notice. An item without ip_address uses an existing consent for its identifier, 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

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 required

Required for individuals using an 18-character CURP; not required for businesses using a 12-character RFC. Used for identity matching and to maximize the probability of recovering data. Must use E.164 format.

emailstring email

Optional. Used for identity matching and to maximize the probability of recovering data.

ip_addressstring

Optional. IP address of the end user when they accepted your privacy notice. When sent, the consent is recorded with this verification under your company's privacy notice, so no prior POST /consents is needed. A new consent is recorded on every request that sends it. Must be a valid IPv4 (e.g., 192.168.2.74) or IPv6 (e.g., 2001:db8::1) address.

Example request

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

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.

Changes

    • breaking

      the request property / became required

    • info

      added the new optional request property /