IMRIMR Registry API

Check a doctor's registration before you rely on it.

One API call tells your event, ethics committee or hospital system whether a registration number is real, which state council issued it, and whose name it belongs to.

Try the live demo Get API access

Current coverage: registrations from 30 state medical councils, 1930 to 2026. The register itself is never published; it is only reachable with an approved API key.

Delegate registration, MedConf Chennai 2026
GET /v1/verify?registration_no=40217&council=Tamil
Event system
IMR API
Medical register
Dr. Kavitha Raman
Reg. no. 40217, Tamil Nadu Medical Council
Verified
Answered in 18 ms. Sample data.

How it works

  1. Request a key

    Tell us who you are and what you are verifying. Once approved, you get a private API key for your system.

  2. Send the number you were given

    Your system calls /v1/verify with the registration number, the council and optionally the name on the form.

  3. Act on a clear answer

    You get back verified: true or false with the matching record, usually in well under a second, so you can approve, flag or ask for documents.

Live demo

This is how a conference registration page could use the API. It runs in a sandbox with made-up doctors, so no real register data is shown.

MedConf Chennai 2026 Delegate registration, doctor rate
Try a sample:
  1. Request sentYour server calls the API with your key
  2. Key and rate limit checkedOnly approved organisations get through
  3. Register searchedNumber, council and name matched
  4. Answer returnedJSON your system can act on
GET /v1/verify
Fill in the form or pick a sample to see the API's response here.

Where it fits

Any process that accepts "I am a registered doctor" on trust can check it instead.

The register stays private

There's no public search. Each organisation gets its own key and only sees the answer to the question it asked.

  • Approved keys only. Every request needs a key we issued, and keys can be switched off at any time.
  • Read-only. The API can look records up but never change them.
  • Per-key limits. Each key has its own requests-per-minute cap, which stops bulk scraping.
  • Every call logged. Who asked, what was asked and when, which is useful for IRB and audit trails.
  • Keys stored hashed. Even a database copy doesn't reveal working keys.

Get API access

Tell us about your organisation and how you'll use verification. We review every request before issuing a key.

Already have a key? Read the API documentation to start integrating.