New optional params for POST /verifications

The POST /verifications endpoint now accepts four new optional fields in the request body: curp, rfc, phone, and email.
These fields provide additional context for the verification process and are not returned in the response.

⚙️ What Changes

New optional request fields — you may now include any combination of the following in your POST /verifications request body:

Field	Type	Description
`curp`	string	CURP of the individual
`rfc`	string	RFC of the individual or business
`phone`	string	Phone number (e.g. `+525512345678`)
`email`	string	Email address

No breaking changes — identifier remains the only required field. Existing integrations continue to work without modification.
Not returned in the response — these fields are accepted for context only. The response body remains unchanged: id, identifier, status, consent_id, created_at, and external_id.

💡 Example Request

{
  "identifier": "ABCD123456HDFABC09",
  "external_id": "client_reference_123",
  "curp": "ABCD123456HDFABC09",
  "rfc": "ABCD123456XYZ",
  "phone": "+525512345678",
  "email": "[email protected]"
}

💡 Example Response

{
  "id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "identifier": "ABCD123456HDFABC09",
  "status": "in_progress",
  "consent_id": "a8b7c9d2-45e3-4f12-b890-123456789abc",
  "created_at": "2026-03-23T14:30:25Z",
  "external_id": "client_reference_123"
}