BHMS Doctor Verification

Endpoint Overview

POST /api/v1/doctor/bhms/verification

Description

The BHMS Doctor Verification API enables real-time validation of Bachelor of Homeopathic Medicine and Surgery (BHMS) doctor credentials across Indian state medical councils. This endpoint verifies the authenticity of BHMS practitioners by validating their registration numbers against official state homeopathy council databases, returning comprehensive professional details including registration dates, qualifications, and degrees.

This API is essential for healthcare platforms, telemedicine services, hospitals, and insurance providers that need to ensure the legitimacy of homeopathic practitioners before onboarding or providing services. By automating the verification process, organizations can reduce manual effort, minimize fraud risks, and maintain compliance with healthcare regulations.

Key Benefits

Instant Verification: Real-time validation of BHMS doctor credentials against official state council records

Comprehensive Data: Retrieves detailed information including registration dates, qualifications, degrees, and parent names

State-Wide Coverage: Supports verification across multiple Indian states with homeopathy councils

Fraud Prevention: Helps identify fake or invalid credentials, protecting patients and healthcare organizations

Use Cases

Healthcare Platforms

Insurance & Pharma

Regulatory & Compliance

Telemedicine Onboarding: Verify BHMS practitioners before allowing them to provide online consultations

Hospital Credentialing: Automate the credentialing process for homeopathic doctors joining healthcare facilities

Medical Directory Services: Validate doctor profiles for online medical directories and appointment booking platforms

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.app

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

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for API authentication (format: `Bearer YOUR_JWT_TOKEN`)
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
state_name	string	Yes	Name of the Indian state where the BHMS doctor is registered (e.g., "chhattisgarh", "maharashtra"). Use lowercase format.
id_number	string	Yes	Registration number of the BHMS doctor as issued by the state homeopathy council. Format and length vary by state.

Example Request

{
    "state_name": "chhattisgarh",
    "id_number": "0002"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object for the verification response
data.client_id	string	Unique identifier for this verification request
data.id_number	string	The registration number that was verified
data.state_name	string	The state name used for verification
data.results	object	Object containing the verified doctor's details
data.results.full_name	string	Complete name of the BHMS doctor including title and parent name
data.results.registration_date	string	Date when the doctor was registered (format: YYYY-MM-DD)
data.results.parent_name	string	Name of the doctor's parent/guardian
data.results.gender	string	Gender of the doctor
data.results.dob	string	Date of birth of the doctor
data.results.birth_place	string	Place of birth of the doctor
data.results.qualification	string	Academic qualifications of the doctor
data.results.degree	string	BHMS degree details including year, month, and issuing council
data.results.college_name	string	Name of the institution where the degree was obtained
data.results.address	string	Registered address of the doctor
data.results.place_of_practice	string	Location where the doctor practices
data.results.renewal_upto	string	Date until which the registration is renewed
data.results.valid_from	string	Start date of registration validity
data.results.valid_upto	string	End date of registration validity
status_code	integer	HTTP status code of the response
success	boolean	Indicates whether the verification was successful
message	string	Human-readable message describing the result
message_code	string	Machine-readable code for the result status

Example Successful Response

{
    "data": {
        "client_id": "bhms_doctor_verification_kAiqMEiRuoEkptTgHvov",
        "id_number": "0002",
        "state_name": "chhattisgarh",
        "results": {
            "full_name": "Dr. Asir Sam Daniel S/o - A.M. Daniel",
            "registration_date": "2003-02-14",
            "parent_name": "",
            "gender": null,
            "dob": null,
            "birth_place": null,
            "qualification": null,
            "degree": "D H M S Aug 1987 State Council of Homoeopathy, Madhyaprdesh (Bhopal)",
            "college_name": null,
            "address": null,
            "place_of_practice": null,
            "renewal_upto": null,
            "valid_from": null,
            "valid_upto": null
        }
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Credentials

Invalid Registration Number

Invalid Request Format

Rate Limit Exceeded

{
    "status_code": 401,
    "success": false,
    "message": "Unauthorized access. Invalid or expired token.",
    "message_code": "unauthorized"
}

This error occurs when the Bearer token is missing, invalid, or expired. Verify that you're using the correct JWT token for your environment.

Integration Best Practices

Security Recommendations

Secure Token Storage: Store JWT tokens securely using environment variables or secure vaults, never hardcode them in your application

Use HTTPS Only: Always make API calls over HTTPS to ensure data encryption in transit

Implement Token Refresh: Set up automatic token refresh mechanisms before expiration to maintain uninterrupted service

API Key Rotation: Regularly rotate your API credentials and update tokens across all environments

Log Sanitization: Ensure sensitive data like tokens and full registration numbers are masked in application logs

Request Validation: Validate and sanitize all input parameters before sending requests to prevent injection attacks

User Experience Guidelines

Show Loading States: Display clear loading indicators during verification as API response times may vary based on state database availability

Handle Null Fields Gracefully: Some fields in the response may be null depending on state council data availability; design UI to handle missing data elegantly

Provide Clear Error Messages: Translate technical error codes into user-friendly messages that guide users on next steps

Cache Verification Results: Consider caching verification results for a reasonable period to improve performance and reduce API calls

Implement Retry Logic: Add exponential backoff retry logic for transient network failures to improve reliability

Display Verification Timestamps: Show users when the verification was last performed for transparency and trust

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

Data Privacy: This API processes sensitive personal information. Ensure compliance with applicable data protection regulations including the Digital Personal Data Protection Act (DPDPA) and maintain proper consent mechanisms for data processing.

Purpose Limitation: Use verification data solely for the stated purpose of credential verification. Do not repurpose or share doctor information without proper authorization.

Data Retention: Implement appropriate data retention policies and securely delete verification records when no longer needed for business purposes.

Audit Trails: Maintain comprehensive logs of all verification requests for compliance auditing and dispute resolution.

State-Specific Regulations: Be aware that homeopathy practice regulations may vary by state. Verification results should be interpreted in context of local regulatory requirements.

Disclaimer Requirements: Consider displaying appropriate disclaimers that verification confirms registration status but does not constitute an endorsement of the practitioner's competence or current practice status.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/doctor/bhms/verification' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "state_name": "chhattisgarh", "id_number": "0002" }'

{ "data": { "client_id": "bhms_doctor_verification_kAiqMEiRuoEkptTgHvov", "id_number": "0002", "state_name": "chhattisgarh", "results": { "full_name": "Dr. Asir Sam Daniel S/o - A.M. Daniel", "registration_date": "2003-02-14", "parent_name": "", "gender": null, "dob": null, "birth_place": null, "qualification": null, "degree": "D H M S Aug 1987 State Council of Homoeopathy, Madhyaprdesh (Bhopal)", "college_name": null, "address": null, "place_of_practice": null, "renewal_upto": null, "valid_from": null, "valid_upto": null } }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses