Send both sides.
One POST, one person's INE. Submit front and back as JPG or PNG with your API key and a unique transaction key.
POST /api/v3/ineMEXICAN CREDENTIALS. ONE CLEAR API.
Two photos in. Structured data out.
Bring INE text into your backend with one simple request.
{
"status": "succeeded",
"needs_review": true,
"data": {
"full_name": "EXAMPLE NAME",
"curp": null,
"address": null
}
}Server-side API keys
Idempotent requests
Encrypted results
Shared usage controls
MADE FOR YOUR BACKEND
Give your application a consistent response to work with, and keep a person in the review loop.
One POST, one person's INE. Submit front and back as JPG or PNG with your API key and a unique transaction key.
POST /api/v3/ineReceive names, CURP, address and other visible text as strings or null. Warnings flag unreadable or conflicting values.
needs_review: trueUse the request ID to retrieve a result during its 23-hour access window. GET and replay use no additional quota.
GET /api/v3/ine/{id}A PLAN FOR YOUR VOLUME
One reserved reading covers one INE, front and back.
Choose annual billing to pay for 10 months upfront, with 12 months of access.
A focused place to start.
Billed monthly · before applicable taxes
Room for your everyday workflows.
Billed monthly · before applicable taxes
For a larger monthly workload.
Billed monthly · before applicable taxes
Have a different monthly volume in mind? Let's talk.
The same operating limits on every plan: 2 concurrent requests and 10 new requests per minute, shared across your company. Monthly quotas reset by UTC calendar month. Reserved attempts consume a reading even if processing fails.
Prices are in MXN, before applicable taxes. Annual plans are paid upfront; readings remain a monthly allowance. Access and billing are arranged by email. No automatic checkout.
BUILT WITH CARE
OCR should make the next step easier without hiding what still needs your attention.
Understand the APIEvery result needs review. OCR does not verify authenticity, the holder's identity or official INE registration status.
Your API key belongs in your backend. The private dashboard uses separate access and shows usage, not extracted personal data.
The API does not store photos. Results are encrypted and available for 23 hours. Expired ciphertext is purged hourly; backups can retain earlier encrypted versions.
LET’S TALK ABOUT YOUR INTEGRATION
Questions about volume or your integration? ecodevcontact@gmail.com