Create Bulk Verifications
Changed onInitiates 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.
Request
- Base URLhttps://api.burodeingresos.com
- AuthAPI key in header X-API-Key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
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}.
Changes
- breaking
the request property
/became required - info
added the new optional request property
/
- breaking