Get State List

Endpoint Overview

GET /api/v1/rera/state-list

Description

The Get RERA State List API provides a comprehensive list of Indian states where RERA (Real Estate Regulatory Authority) verification services are available, along with the supported document types for verification. This endpoint serves as a reference catalog that enables developers to understand the geographical coverage of RERA verification services and build dynamic user interfaces with accurate state selection options.

RERA was established under the Real Estate (Regulation and Development) Act, 2016, to regulate the real estate sector and protect homebuyers' interests. This API helps organizations integrate RERA verification capabilities by first identifying which states and document types are supported, making it an essential prerequisite for implementing RERA verification workflows.

Key Benefits

Dynamic State Discovery: Automatically retrieve the current list of supported states without hardcoding values in your application

Document Type Reference: Identify available verification types (agents and projects) to build appropriate verification workflows

Future-Proof Integration: Stay updated with newly added states as RERA coverage expands across India

Simplified UI Development: Use the response to populate dropdown menus and selection fields dynamically

Use Cases

Real Estate Platforms

Financial Services

PropTech Solutions

Build property listing platforms with state-specific RERA verification filters

Validate real estate agents and projects during onboarding processes

Create dynamic search interfaces allowing users to filter properties by RERA-registered states

Implement compliance checks for property listings to ensure RERA registration requirements are met

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 authentication. Format: `Bearer {JWT_TOKEN}`

Request Body

This is a GET request and does not require a request body.

Example Request

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object holding the response data
data.states	array	Array of state identifiers where RERA verification is available. Values are in snake_case format (e.g., "uttar_pradesh")
data.document_type	array	Array of supported document types for RERA verification. Values: "agent" (for RERA-registered agents), "project" (for RERA-registered projects)
status_code	integer	HTTP status code of the response (200 for success)
message_code	string	Machine-readable code for the response status
message	string	Human-readable message describing the result
success	boolean	Indicates whether the request was successful

Example Successful Response

{
    "data": {
        "states": [
            "uttar_pradesh",
            "kerala",
            "assam",
            "west_bengal",
            "madhya_pradesh",
            "bihar",
            "chhattisgarh",
            "delhi",
            "karnataka",
            "uttarakhand",
            "maharashtra",
            "gujarat",
            "haryana",
            "telangana"
        ],
        "document_type": [
            "agent",
            "project"
        ]
    },
    "status_code": 200,
    "message_code": "success",
    "message": "Success",
    "success": true
}

Possible Error Responses

Authentication Error

Server Error

Service Unavailable

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

Occurs when the JWT bearer token is missing, invalid, or has expired. Regenerate your token and retry the request.

Integration Best Practices

Security Recommendations

Secure Token Storage: Store JWT tokens securely using environment variables or secure credential management systems

Token Caching: Cache tokens appropriately to reduce token generation requests while respecting expiration times

HTTPS Only: Always use HTTPS for API calls to ensure data encryption in transit

Least Privilege Access: Grant API access only to systems and users that require RERA verification functionality

Audit Logging: Maintain logs of API calls for security auditing and troubleshooting purposes

User Experience Guidelines

Response Caching: Cache the state list locally as it changes infrequently, reducing unnecessary API calls

Display Name Mapping: Convert snake_case state identifiers to user-friendly display names (e.g., "uttar_pradesh" → "Uttar Pradesh")

Alphabetical Sorting: Sort states alphabetically in your UI for better user experience

Graceful Degradation: If the API call fails, provide a fallback list or clear error messaging

Lazy Loading: Fetch the state list only when needed rather than on application startup

Code Samples

cURL

Python

Node.js

Compliance and Legal Considerations

The Real Estate (Regulation and Development) Act, 2016 (RERA) mandates that:

All real estate projects exceeding 500 square meters or comprising eight apartments must be registered with the state RERA authority

Real estate agents must obtain RERA registration to facilitate property transactions

Developers must provide accurate project information and maintain transparency with buyers

Failure to register under RERA can result in penalties and legal action

When integrating RERA verification:

Data Accuracy: State identifiers returned by this API reflect current coverage and may expand as more states implement RERA portals

Verification Requirements: Both document types (agent and project) have distinct verification requirements and response structures

State-Specific Rules: Each state may have additional regulations and requirements beyond central RERA provisions

Data Retention: Maintain verification records as required by your organization's compliance and audit policies

User Consent: Ensure appropriate consent is obtained before performing RERA verifications on behalf of users

Regular Updates: Check this endpoint periodically as new states may be added when their RERA portals become available

This API serves as a foundational reference for building compliant real estate verification systems that adhere to Indian regulatory requirements.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

{ "data": { "states": [ "uttar_pradesh", "kerala", "assam", "west_bengal", "madhya_pradesh", "bihar", "chhattisgarh", "delhi", "karnataka", "uttarakhand", "maharashtra", "gujarat", "haryana", "telangana" ], "document_type": [ "agent", "project" ] }, "status_code": 200, "message_code": "success", "message": "Success", "success": true }

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