NMC Doctor Lookup API - India NMC Registration Verification

Verify Indian doctor registration numbers against the National Medical Commission (NMC) Indian Medical Register (IMR). This Apify actor provides a fast NMC doctor lookup API for registration verification, batch checks, and optional doctor search by name, registration year, or State Medical Council.

The actor uses the public NMC IMR JSON endpoints directly. It does not use browser automation, so registration-number checks are usually much faster than page scraping.

What This Actor Does

• Verifies one doctor registration number against NMC IMR.
• Verifies many registration numbers in one run.
• Searches NMC doctors by name, registration year, State Medical Council ID, or council name.
• Fetches detailed NMC records when a unique registration match is found.
• Returns structured JSON for KYC, healthcare onboarding, credential checks, compliance workflows, and internal verification tools.

Best For

• NMC doctor registration verification in India.
• Indian Medical Register lookup by registration number.
• Doctor credential checks for hospitals, clinics, healthtech, insurance, lending, and compliance teams.
• Batch verification of doctor registration numbers.
• Advanced NMC doctor search when only name, year, or council information is available.

Data Source

The source is the official NMC Indian Medical Register:

• NMC IMR page: https://www.nmc.org.in/information-desk/indian-medical-register/
• NMC API base: https://www.nmc.org.in/MCIRest

This actor is not affiliated with or endorsed by the National Medical Commission. It only automates lookup against public NMC IMR data.

Inputs

Verification is selected when registrationId or registrationIds is present. Search mode is selected when no registration ID is present and at least one advanced filter is provided.

Verify One Registration

{
  "registrationId": "2000010031",
  "stateMedicalCouncil": "Maharashtra Medical Council"
}

Batch Verify

{
  "registrationIds": ["2000010031", "12345"],
  "maxConcurrency": 3,
  "delayMs": 100,
  "allowInsecureTls": true
}

Advanced Search

{
  "name": "salunkhe",
  "year": 2000,
  "maxResults": 25,
  "includeDetails": false
}

For precise council search, pass stateMedicalCouncilId when you know the NMC smcId. stateMedicalCouncil is useful for registration disambiguation and post-filtering search results by council name.

Input Fields

Field	Mode	Description
registrationId	Verify	One NMC doctor registration number.
registrationIds	Verify	Batch list of registration numbers.
name	Search	Doctor name filter for NMC search.
year	Search	Registration year from 1947 to the current year.
stateMedicalCouncil	Verify/Search	Council name for duplicate registration disambiguation or search filtering.
stateMedicalCouncilId	Search/Verify	Official NMC smcId for precise council filtering.
includeDetails	Search	Fetch detailed NMC data for each candidate row.
includeRaw	Both	Include raw NMC row/detail payloads for audit.
maxResults	Search	Maximum candidate rows to emit.
maxConcurrency	Verify	Concurrent verification workers.
delayMs	Both	Optional polite delay after detail requests.
requestTimeoutSecs	Both	Timeout per NMC request. Defaults to 120 seconds because NMC can respond slowly.
maxRetries	Both	Retry attempts after failed NMC requests.
allowInsecureTls	Both	Use only if Node rejects NMC's certificate chain.

Output

Verify mode emits one item per registration number:

{
  "mode": "verify",
  "query": {
    "registrationId": "2000010031"
  },
  "status": "valid",
  "isValid": true,
  "doctorName": "salunkhe deepak vasantrao",
  "registrationId": "2000010031",
  "nmcDoctorId": 3631,
  "stateMedicalCouncil": "Maharashtra Medical Council",
  "registrationDate": "10/01/2000",
  "yearInfo": 2000,
  "qualification": "MBBS",
  "source": "NMC Indian Medical Register"
}

Search mode emits candidate records with status: "candidate" and isValid: null.

Output Fields

Common verification output fields include:

• status
• isValid
• doctorName
• registrationId
• nmcDoctorId
• stateMedicalCouncil
• registrationDate
• yearInfo
• qualification
• qualificationYear
• university
• parentName
• dateOfBirth
• uprnNo
• address
• additionalQualifications
• source
• sourceUrl
• checkedAt

Statuses

• valid: one exact registration match was found and detail was fetched.
• removed: NMC detail marks the registration as removed.
• restored: NMC detail marks the registration as restored.
• not_found: no exact registration match was found.
• ambiguous: multiple exact registration matches were found; pass stateMedicalCouncil.
• candidate: search-mode result, not a verified identity.
• error: a per-record lookup failed.

Verification vs Search

Use registration verification when you need a reliable result. NMC registration numbers can collide across State Medical Councils, so the actor exact-matches registration numbers and returns ambiguous when more than one council has the same registration number. Pass stateMedicalCouncil to disambiguate.

Use search mode when you are exploring candidates by name, year, or council. Search results are not marked as verified identities because name-based matching can return multiple doctors.

TLS

Secure TLS verification is enabled by default. At the time of testing, Node can reject the NMC certificate chain with unable to verify the first certificate. If that happens in the Apify runtime, rerun with:

{
  "registrationId": "2000010031",
  "allowInsecureTls": true
}

Only use this flag when needed.

Example Use Cases

• Verify a doctor before onboarding to a healthtech platform.
• Check doctor credentials for healthcare KYC.
• Validate registration details during insurance or lending workflows.
• Search NMC IMR candidates by doctor name and registration year.
• Build an internal NMC doctor verification API without maintaining browser automation.

Notes

• Registration verification is the fastest and most deterministic path.
• Broad name searches can return many candidates.
• The actor writes one dataset item per verification result or search candidate.
• Public NMC availability and response shape can change; use includeRaw for audit/debugging if needed.