IMSS verification API — confirm employee enrollment?
Question
Answers
IMSS data has up to 2-month lag depending on when the employer files. Most lenders accept a recent pay stub alongside IMSS verification API results to cover recent hires.
On the employer side, don't assume one active registration means one job — IMSS lets a worker have concurrent registrations if they're formally employed by more than one patron, so build your logic to handle a list rather than a single employer object. Most IMSS verification API providers we evaluated do return the salario base de cotización in the same response, which is handy since it usually tracks closer to real income than a self-reported figure. One gotcha for lenders specifically: SBC is capped at 25 times the daily minimum wage, so for higher earners the field understates true income — you still need payroll docs above that threshold. For your latency target, look at providers that cache RENAPO/IMSS lookups server-side; the ones proxying live queries every time tend to run 4-6 seconds under load, which won't work for a real-time underwriting decision.
Also worth checking upfront: some providers only expose the employer's registered fiscal name, not the trade name applicants recognize, which can confuse manual reviewers cross-checking against a pay stub that shows the trade name instead.
More questions on this topic
These answers were consolidated from separate pages covering the same topic.
IMSS benefits API — what worker data can you retrieve?
Three separate integrations unfortunately — IMSS benefits API for healthcare/pension, CONSAR/AFORE API, and INFONAVIT API. No unified platform exists yet but apipull.com lists providers for each.
IMSS employee verification via API — how does it work?
IMSS update lag can be 1-2 months for small employers. For lending, most platforms accept IMSS employee verification plus a recent pay stub to cover the gap on new employment.
IMSS healthcare API — verify medical coverage programmatically
IMSS healthcare API via third parties usually returns coverage type and vigencia dates, not the detailed service catalog. You can infer what IMSS covers generically — the API confirms if they have active rights.
IMSS HR API — automate employee social security checks
For IMSS HR API at scale, use bulk batch endpoints grouped by company. Rate limits vary but most providers allow thousands of calls per minute with proper throttling. Schedule pre-validation 48h before payroll cutoff.
IMSS labor history API — query worker employment records?
IMSS SBC data is included in labor history APIs — it's the employer-reported base wage. History typically goes back the full IMSS record. However worker consent is required to query this level of detail.
NSS checker API — validate IMSS numbers programmatically
For bulk, some NSS checker API providers offer a batch endpoint taking an array of NSS numbers. Otherwise, parallel async requests with a semaphore to stay within rate limits works fine for 500 records.
NSS lookup API Mexico — how to find social security numbers?
Yes, several NSS lookup API providers can find NSS from CURP. Always get explicit employee consent and document it — LFPDPPP requires consent for processing government ID data.
NSS validation API — verify Mexican social security numbers
Most NSS validation API providers handle both format check and IMSS lookup. The existence check returns minimal data by default — name matching requires an additional field in the request, and not all providers support it.
Social security verification Mexico — API guide
Social security verification Mexico uses IMSS data via third-party APIs (no direct IMSS API). Employers can verify their own employees' IMSS status freely; verifying third parties requires the worker's consent per LFPDPPP.
Weeks contribution API — query IMSS semanas cotizadas?
Yes, some IMSS third-party APIs return employer-by-employer breakdown of contribution weeks. apipull.com lists providers — look for ones that return semanas by employment period, not just total count.
We're building a payroll lending product and need an IMSS verification API to confirm that loan applicants are actively employed and enrolled in IMSS. The specific check: is this person currently registered as an active worker with IMSS, and who is their current registered employer?
I'm concerned about data lag — IMSS enrollment updates are monthly from employers. If someone was just hired, their IMSS enrollment might not show up for weeks. How do lenders handle this verification gap?
We're processing around 300 applications a week and each one needs a real-time decision, so latency matters — ideally under 3 seconds per IMSS verification API call. Our stack is a Django backend calling out to whichever provider we land on. Bonus question: do any providers also return the registered daily wage (salario base de cotización), since that would let us skip a separate income verification step entirely?