Doctor Verification

Endpoint Overview

POST /api/v1/doctor/doctor-verification

Description

This API endpoint allows you to verify a doctor's credentials by providing their registration number and registration year. The service validates the information against official medical council records and returns comprehensive details about the doctor, including their qualifications, registration date, and personal information.

Key Benefits

Instant verification of doctor credentials against official medical council databases

Comprehensive doctor information including qualifications and registration details

Secure and reliable verification process with unique client ID tracking

Streamlined KYC process for healthcare platforms and services

Use Cases

Healthcare Platforms

Insurance

Hospitals & Clinics

Verify doctors before onboarding them to telemedicine platforms

Validate credentials for doctor listing directories

Confirm doctor identity for medical consultation services

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.io

Production: https://kyc-api.surepass.io

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for authentication (JWT format)
Content-Type	Yes	application/json

Request Body

Parameter	Type	Required	Description
registration_number	String	Yes	Doctor's registration number issued by the medical council
registration_year	String	Yes	Year when the doctor was registered with the medical council

Example Request

{
    "registration_number": "12345",
    "registration_year": "1900"
}

Process Response

Response Parameters

Parameter	Type	Description
data	Object	Contains the verification results and doctor information
data.client_id	String	Unique identifier for this verification request
data.registration_number	String	Doctor's registration number (as provided in request)
data.registration_year	String	Doctor's registration year (as provided in request)
data.results	Array	Array containing detailed doctor information
status_code	Number	HTTP status code of the response
success	Boolean	Indicates if the verification was successful
message	String	Human-readable status message
message_code	String	Machine-readable status code

Results Object Parameters

Parameter	Type	Description
registration_date	String	Doctor's registration date in "YYYY-MM-DD" format
doctor_id	String	Unique identifier for the doctor in the medical council records
full_name	String	Doctor's complete name including title
dob	String	Doctor's date of birth in "YYYY-MM-DD" format
address	String	Doctor's registered address
parent_name	String	Doctor's parent name (may be null)
state_medical_council	String	Name of the state medical council where the doctor is registered
university	String	University from which the doctor obtained their qualification
qualification	String	Doctor's highest medical qualification
year_of_passing	String	Year when the doctor passed their qualification

Example Successful Response

{
    "data": {
        "client_id": "doctor_bYrsAyympURxdawVnegy",
        "registration_number": "12345",
        "registration_year": "1900",
        "results": [
            {
                "registration_date": "1900-00-00",
                "doctor_id": "00001",
                "full_name": "Dr. Rustom",
                "dob": "1800-01-01",
                "address": "Vasai District Thane",
                "parent_name": null,
                "state_medical_council": "Tamil Nadu Medical Council",
                "university": "university",
                "qualification": "MBBS",
                "year_of_passing": "1900"
            }
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Credentials

Authentication Error

Server Error

{
    "status_code": 400,
    "success": false,
    "message": "Invalid doctor registration details",
    "message_code": "invalid_registration_details"
}

Returned when the provided registration number or year doesn't match any records.

Integration Best Practices

Security Recommendations

Store JWT tokens securely and never expose them in client-side code

Implement proper error handling to manage failed verification attempts

Rotate JWT tokens periodically and don't hardcode them in your application

Use HTTPS for all API communications to ensure data encryption in transit

User Experience Guidelines

Implement form validation to ensure registration numbers and years are in the correct format

Display a user-friendly loading state during the verification process

Provide clear error messages when verification fails

Consider caching verified doctor details to improve performance for repeat lookups

Code Samples

cURL

Python

Node.js

Related APIs

Medical Council Verification API: Verify medical council registration details

Healthcare Professional KYC API: Complete KYC verification for healthcare professionals

Hospital Verification API: Verify hospital registration and accreditation details

Compliance and Legal Considerations

This API accesses personal and professional information of medical practitioners. Ensure you have appropriate consent and legal basis for processing this data. The information should be used in compliance with applicable healthcare regulations, data protection laws, and privacy policies. Usage of this API may be subject to medical council guidelines and healthcare information handling regulations.

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/doctor/doctor-verification' \ --header 'Authorization: Bearer TOKEN' \ --header 'Content-Type: application/json' \ --data-raw '{ "registration_number": "12345", "registration_year": "1900" }'

{ "data": { "client_id": "doctor_bYrsAyympURxdawVnegy", "registration_number": "12345", "registration_year": "1900", "results": [ { "registration_date": "1900-00-00", "doctor_id": "00001", "full_name": "Dr. Rustom", "dob": "1800-01-01", "address": "Vasai District Thane", "parent_name": null, "state_medical_council": "Tamil Nadu Medical Council", "university": "university", "qualification": "MBBS", "year_of_passing": "1900" } ] }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Doctor Verification

Doctor Verification#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Results Object Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses

Doctor Verification

Description

Use Cases

Technical Implementation

Request Headers

Request Body

Example Request

Response Parameters

Results Object Parameters

Example Successful Response

Possible Error Responses

Integration Best Practices

Code Samples