Changelog
🧾 New fields for invoices
Starting June 8, 2026, the Invoices API will return additional fields with richer detail for ingreso and egreso invoices, as well as for nomina income and deduction concepts.
🔄 Updates to POST /consents & /verifications
Several improvements shipped across POST /consents and POST /verifications — IPv6 support, a CURP-only identifier rule for individuals, and client-provided RFC for invoice extraction — plus three new Sandbox Business RFCs for end-to-end integration testing.
⚠️ Stop emitting of the `verification.historical` webhook event
Originally, verification.historical existed to deliver data early when IMSS verification was slow. That process is now much faster, and the same data is already available in verification.completed, which arrives almost immediately. Keeping both events only meant receiving duplicate notifications for the same information.
🔍 New query param: `institution` on GET / profile and GET /employments
🏢 New endpoint: GET /business-profile/{identifier}
- Buró de Ingresos now supports business (RFC) identifiers across two endpoints: a new dedicated business profile endpoint and expanded invoice support for business entities.
- These changes enable clients to retrieve structured business identity data and invoice history for legal entities, not just individuals.
💳 New parameter: include_payment_info on GET /invoices
➕ Optional params for POST /verifications
💰New Field: estimated_monthly_income in /profile
🔒 TLS 1.3 Minimum Enforcement
Upgrading to TLS 1.3 strengthens the security of data transmitted between Buró de Ingresos and your systems, and aligns us with the standards required by regulators and our clients.
