Karnataka Drug License - District List

Endpoint Overview

GET /api/v1/corporate/karnataka-drug-license/district-list

Description

The Karnataka Drug License District List API provides a comprehensive list of all administrative districts and sub-divisions (ADCs - Assistant Drug Controllers) in Karnataka state where drug licenses are issued and managed. This endpoint serves as a reference data API that returns standardized district codes used throughout the Karnataka drug licensing system.

This API is essential for applications that need to interact with Karnataka's pharmaceutical regulatory framework, enabling developers to populate dropdown menus, validate district selections, and ensure data consistency across drug license-related operations. The district codes returned by this API are used as reference values in other Karnataka drug license verification and application APIs.

Key Benefits

Comprehensive Coverage: Access all 57 district and sub-division codes across Karnataka

Standardized Codes: Use official district identifiers recognized by Karnataka drug licensing authorities

Zero Input Required: Simple GET request with no parameters needed

Reference Data: Essential for building user interfaces and validating district selections in drug license applications

Use Cases

Pharmaceutical Industry

Healthcare Technology

Government & Fintech

License Application Systems: Populate district selection dropdowns in drug license application portals

Multi-location Management: Manage drug licenses across multiple districts for pharmaceutical distributors and manufacturers

Compliance Tracking: Track and organize licenses by administrative jurisdiction

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 YOUR_JWT_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

This endpoint does not require any request body parameters. It is a simple GET request that returns the complete list of districts.

Example Request

No request body required for this GET endpoint

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object for the response data
data.districts	array[string]	Array of district codes representing all administrative divisions in Karnataka where drug licenses are managed
status_code	integer	HTTP status code of the response (200 for success)
message_code	string	Machine-readable status code (e.g., "success")
message	string	Human-readable status message
success	boolean	Indicates whether the API call was successful

Example Successful Response

{
    "data": {
        "districts": [
            "bangalore_1_adc1",
            "bangalore_1_adc2",
            "bangalore_2_adc1",
            "bangalore_2_adc2",
            "bangalore_3_adc1",
            "bangalore_3_adc2",
            "bangalore_4_adc1",
            "bangalore_4_adc2",
            "bangalore_5_adc1",
            "bangalore_5_adc2",
            "bangalore_6_adc1",
            "bangalore_6_adc2",
            "bidar_adc1",
            "bidar_adc2",
            "bellary_adc",
            "vijayanagara_adc",
            "belgaum_adc1",
            "belgaum_adc2",
            "belgaum_adc3",
            "bijapur_adc1",
            "bijapur_adc2",
            "bangalore_rural",
            "bagalkot_adc1",
            "bagalkot_adc2",
            "chikkaballapur",
            "chitradurga",
            "kodagu",
            "chickmagalore",
            "chamarajanarar",
            "davanagere_adc1",
            "davanagere_adc2",
            "gadag",
            "gulbarga_adc1",
            "gulbarga_adc2",
            "dharwad_adc1",
            "dharwad_adc2",
            "hassan",
            "haveri",
            "kolar",
            "koppal",
            "uttara_kannada",
            "mandya",
            "mangalore_adc1",
            "mangalore_adc2",
            "mysore_1",
            "mysore_2",
            "bangalore_reg",
            "raichur_adc1",
            "raichur_adc2",
            "ramanagara",
            "shimogga_adc1",
            "shimogga_adc2",
            "sib_circle",
            "tumkur_adc1",
            "tumkur_adc2",
            "udupi",
            "yadgiri"
        ]
    },
    "status_code": 200,
    "message_code": "success",
    "message": "Success",
    "success": true
}

Possible Error Responses

Unauthorized (401)

Forbidden (403)

Internal Server Error (500)

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

This error occurs when the JWT Bearer token is missing, invalid, or expired. Verify your authentication credentials and regenerate the token if necessary.

Integration Best Practices

Security Recommendations

Secure Token Storage: Never expose JWT tokens in client-side code or public repositories. Store tokens securely in environment variables or secure credential management systems

Token Rotation: Implement token refresh mechanisms and rotate tokens periodically to minimize security risks

HTTPS Only: Always use HTTPS endpoints to ensure encrypted communication between your application and the API

Rate Limiting: Implement appropriate rate limiting and caching strategies to avoid unnecessary API calls

Environment Separation: Use separate tokens for sandbox and production environments, and never use production tokens in development

User Experience Guidelines

Cache District Data: Since district lists rarely change, cache the response locally to improve application performance and reduce API calls

Display User-Friendly Names: Transform district codes (e.g., "bangalore_1_adc1") into readable formats (e.g., "Bangalore 1 - ADC 1") for better user experience

Implement Search and Filter: For applications with district selection, implement search and autocomplete functionality to help users quickly find their district

Load on Initialization: Fetch district data during application initialization or user session start rather than on-demand to ensure smooth user interactions

Graceful Error Handling: Display user-friendly error messages if the API is unavailable, and consider providing offline fallback data for critical applications

Code Samples

cURL

Python

Node.js

Related APIs

Karnataka Drug License Verification API: Verify the authenticity and status of drug licenses issued in Karnataka using license numbers and district codes obtained from this API.

Karnataka Drug License Details API: Retrieve comprehensive details about a specific drug license including holder information, business details, and license validity.

Corporate Verification Suite: Access other corporate verification APIs for business validation, GST verification, and regulatory compliance checks.

Compliance and Legal Considerations

This API provides reference data for administrative districts in Karnataka as recognized by the state's drug control authorities. The district codes are standardized identifiers used in official drug licensing processes. Organizations using this API should ensure compliance with the Drugs and Cosmetics Act, 1940, and Karnataka state regulations governing pharmaceutical businesses. The district list may be updated periodically to reflect administrative changes; applications should refresh cached data regularly. This API is intended for legitimate business verification and compliance purposes only. Misuse of district data or associated license information for fraudulent activities is prohibited and may result in legal action. Always obtain necessary consents and follow data protection regulations when processing business information related to drug licenses.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

{ "data": { "districts": [ "bangalore_1_adc1", "bangalore_1_adc2", "bangalore_2_adc1", "bangalore_2_adc2", "bangalore_3_adc1", "bangalore_3_adc2", "bangalore_4_adc1", "bangalore_4_adc2", "bangalore_5_adc1", "bangalore_5_adc2", "bangalore_6_adc1", "bangalore_6_adc2", "bidar_adc1", "bidar_adc2", "bellary_adc", "vijayanagara_adc", "belgaum_adc1", "belgaum_adc2", "belgaum_adc3", "bijapur_adc1", "bijapur_adc2", "bangalore_rural", "bagalkot_adc1", "bagalkot_adc2", "chikkaballapur", "chitradurga", "kodagu", "chickmagalore", "chamarajanarar", "davanagere_adc1", "davanagere_adc2", "gadag", "gulbarga_adc1", "gulbarga_adc2", "dharwad_adc1", "dharwad_adc2", "hassan", "haveri", "kolar", "koppal", "uttara_kannada", "mandya", "mangalore_adc1", "mangalore_adc2", "mysore_1", "mysore_2", "bangalore_reg", "raichur_adc1", "raichur_adc2", "ramanagara", "shimogga_adc1", "shimogga_adc2", "sib_circle", "tumkur_adc1", "tumkur_adc2", "udupi", "yadgiri" ] }, "status_code": 200, "message_code": "success", "message": "Success", "success": true }

District

Karnataka Drug License - District List#

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