BDS MDS Doctor Verification

Endpoint Overview

POST /api/v1/doctor/bds-mds/verification

Description

The BDS/MDS Doctor Verification API enables real-time verification of dental practitioners registered with State Dental Councils across India. This endpoint validates the credentials of dentists holding Bachelor of Dental Surgery (BDS) or Master of Dental Surgery (MDS) degrees by cross-referencing their registration details with official state dental council databases.

This API retrieves comprehensive information including the practitioner's personal details, educational qualifications, registration dates, and practice addresses. It serves as a critical tool for healthcare organizations, insurance providers, and telemedicine platforms to verify the authenticity of dental practitioners before onboarding or processing claims.

The verification process is instantaneous, providing structured data that can be seamlessly integrated into compliance workflows, credentialing systems, and patient safety protocols.

Key Benefits

Instant Verification: Real-time validation of dental practitioner credentials across multiple state councils, eliminating manual verification delays

Comprehensive Data: Access detailed information including qualifications, registration dates, specializations, and practice addresses in a structured format

Regulatory Compliance: Ensure adherence to healthcare regulations by verifying practitioner credentials before service delivery or claims processing

Fraud Prevention: Reduce risk of credential fraud by validating registration numbers directly against official state dental council records

Use Cases

Healthcare Platforms

Insurance & Claims

HR & Recruitment

Telemedicine Onboarding: Verify dental practitioners during platform registration to ensure only licensed professionals provide remote consultations

Hospital Credentialing: Automate the credentialing process for dental departments by validating BDS/MDS qualifications and registration status

Multi-location Clinics: Verify credentials of dental practitioners across different branches to maintain consistent quality standards

Referral Networks: Validate specialists' credentials before adding them to referral networks for specialized dental procedures

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	The name of the state where the dental practitioner is registered. Use lowercase format with underscores (e.g., "maharashtra", "andhra_pradesh"). Refer to the state list API for supported states
id_number	string	Yes	The unique registration number assigned to the dental practitioner by the respective State Dental Council (e.g., "A-101", "MH/12345")

Example Request

{
  "state_name": "maharashtra",
  "id_number": "A-101"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Contains the complete verification results and metadata
data.client_id	string	Unique identifier for this verification request, useful for tracking and auditing purposes
data.id_number	string	The registration number that was verified
data.state_name	string	The state name used for verification
data.results	object	Contains all verified information about the dental practitioner
data.results.name	string	Full name of the dental practitioner as registered with the dental council
data.results.registration_date	string	Date when the practitioner was first registered (format: YYYY-MM-DD)
data.results.father_name	string	Father's name of the practitioner (may be null if not available)
data.results.mother_name	string	Mother's name of the practitioner (may be null if not available)
data.results.gender	string	Gender of the practitioner (e.g., "Male", "Female")
data.results.dob	string	Date of birth of the practitioner (format: YYYY-MM-DD)
data.results.qualification	array	Array of qualification objects containing educational details
data.results.qualification[].degree	string	Degree earned (e.g., "B.D.S.", "M.D.S.", "L.D.S.C.")
data.results.qualification[].specialization	string	Specialization field if applicable (e.g., "Orthodontics", "Oral Surgery")
data.results.qualification[].college	string	Name of the dental college where the degree was obtained
data.results.qualification[].university	string	University that awarded the degree
data.results.qualification[].year_of_passing	string	Year when the degree was completed
data.results.qualification[].registration_date	string	Date when this particular qualification was registered
data.results.address_in_parts	object	Structured address information broken into components
data.results.address_in_parts.address_line_1	string	Primary address line (building/house name)
data.results.address_in_parts.address_line_2	string	Secondary address line (locality/area)
data.results.address_in_parts.address_line_3	string	Additional address information
data.results.address_in_parts.address_line_4	string	Additional address information
data.results.address_in_parts.address_code	string	Internal address code (may be "0" if not applicable)
data.results.address_in_parts.city	string	City or district name
data.results.address_in_parts.postal_code	string	PIN code/postal code
data.results.address_in_parts.state	string	State name in title case format
data.results.address_in_parts.country	string	Country name (typically "India")
data.results.address_in_parts.landmark	string	Nearby landmark for address reference
data.results.address_in_parts.additional_info_1	string	Additional address information field
data.results.address_in_parts.additional_info_2	string	Additional address information field
data.results.address	string	Full address as a single string (may be null if address_in_parts is populated)
data.results.valid_upto	string	Registration validity date if applicable (may be null for lifetime registrations)
status_code	integer	HTTP status code (200 for successful verification)
success	boolean	Indicates whether the API call was successful (true/false)
message	string	Human-readable message describing the result
message_code	string	Machine-readable code for the result status

Example Successful Response

{
  "data": {
    "client_id": "bds_mds_doctor_verification_AmpRAFnAvdGXvlIjpyry",
    "id_number": "A-101",
    "state_name": "maharashtra",
    "results": {
      "name": "Rustam Dinshawji Umrigar",
      "registration_date": "1800-01-01",
      "father_name": null,
      "mother_name": null,
      "gender": "Male",
      "dob": "1949-11-25",
      "qualification": [
        {
          "degree": "B.D.S.",
          "specialization": "",
          "college": "Bharati Vidyapeeth Dental College And Hospital",
          "university": "Bharati Vidyapeeth (Deemed University)",
          "year_of_passing": "2020",
          "registration_date": "2020-02-29"
        },
        {
          "degree": "L.D.S.C.",
          "specialization": "",
          "college": "",
          "university": "",
          "year_of_passing": "1943",
          "registration_date": "1800-01-01"
        }
      ],
      "address_in_parts": {
        "address_line_1": "KISMAT 3RD FLOOR, OPP SASSOOM DOEKS",
        "address_line_2": "COLABA",
        "address_line_3": "",
        "address_line_4": "",
        "address_code": "0",
        "city": "Mumbai Suburban",
        "postal_code": "400005",
        "state": "Maharashtra",
        "country": "India",
        "landmark": "",
        "additional_info_1": "",
        "additional_info_2": ""
      },
      "address": null,
      "valid_upto": null
    }
  },
  "status_code": 200,
  "success": true,
  "message": "Success",
  "message_code": "success"
}

Possible Error Responses

Invalid Credentials

Invalid State

Missing Parameters

{
  "status_code": 401,
  "success": false,
  "message": "Invalid authentication token",
  "message_code": "unauthorized"
}

Occurs when the Bearer token is missing, expired, or invalid. Verify your JWT token and ensure it's correctly included in the Authorization header.

Integration Best Practices

Security Recommendations

Token Security: Store JWT tokens securely using environment variables or secure vaults; never hardcode tokens in source code or commit them to version control

HTTPS Only: Always use HTTPS endpoints for API calls to ensure data is encrypted in transit and protected from man-in-the-middle attacks

Token Rotation: Implement regular token rotation policies and refresh mechanisms to minimize the impact of potential token compromise

Data Encryption: Encrypt sensitive verification data at rest in your databases and implement appropriate access controls

Rate Limiting: Implement client-side rate limiting to avoid exceeding API quotas and ensure fair usage across your application

Audit Logging: Maintain comprehensive logs of all verification requests including timestamps, user contexts, and results for compliance and security audits

User Experience Guidelines

Pre-validation: Use the State List API to populate dropdown menus, ensuring users can only select from supported states

Format Guidance: Provide clear examples of registration number formats for different states to reduce input errors

Loading States: Display appropriate loading indicators during API calls, as verification typically completes within 2-3 seconds

Error Handling: Show user-friendly error messages when verification fails, guiding users to correct input mistakes or contact support

Result Display: Present verification results in a clear, scannable format highlighting key information like name, qualification, and registration status

Retry Logic: Implement exponential backoff retry mechanisms for transient failures while avoiding excessive retry attempts that could impact rate limits

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

This API accesses publicly available information from State Dental Council registries for verification purposes. Organizations using this API must ensure compliance with applicable data protection regulations including the Digital Personal Data Protection Act, 2023 (DPDPA). The verification should be conducted with proper consent from the dental practitioners being verified, and the retrieved information should be used solely for legitimate business purposes such as credentialing, onboarding, or compliance verification. Organizations are responsible for implementing appropriate data retention policies and ensuring that verified data is stored securely and not shared with unauthorized parties. The API should not be used for unauthorized background checks or any purpose that violates individual privacy rights or applicable healthcare regulations.

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/bds-mds/verification' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "state_name": "maharashtra", "id_number": "A-101" }'

{ "data": { "client_id": "bds_mds_doctor_verification_AmpRAFnAvdGXvlIjpyry", "id_number": "A-101", "state_name": "maharashtra", "results": { "name": "Rustam Dinshawji Umrigar", "registration_date": "1800-01-01", "father_name": null, "mother_name": null, "gender": "Male", "dob": "1949-11-25", "qualification": [ { "degree": "B.D.S.", "specialization": "", "college": "Bharati Vidyapeeth Dental College And Hospital", "university": "Bharati Vidyapeeth (Deemed University)", "year_of_passing": "2020", "registration_date": "2020-02-29" }, { "degree": "L.D.S.C.", "specialization": "", "college": "", "university": "", "year_of_passing": "1943", "registration_date": "1800-01-01" } ], "address_in_parts": { "address_line_1": "KISMAT 3RD FLOOR, OPP SASSOOM DOEKS", "address_line_2": "COLABA", "address_line_3": "", "address_line_4": "", "address_code": "0", "city": "Mumbai Suburban", "postal_code": "400005", "state": "Maharashtra", "country": "India", "landmark": "", "additional_info_1": "", "additional_info_2": "" }, "address": 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