Create Verification

post

https://api.burodeingresos.com/verifications

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

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Identifier for the verification. Use an 18-char CURP for individuals or a 12-char RFC for businesses. Phone is required for individuals using an 18-char CURP and is not required for businesses using a 12-char RFC. It is used for identity matching and to maximize the probability of recovering data. Phone must use E.164 format. rfc and email remain optional.

identifier

string

required

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

external_id

string

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

rfc

string

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.

phone

string

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.

string

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

Responses

202Verification 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.

400Bad Request - Validation error, such as consent required but not found for the identifier.

401Unauthorized - Invalid or missing API key.