What does this API do?
The Property Search Report API (provided by TEAL India, service code 114) enables lenders to digitally initiate and retrieve property due diligence reports. Three report types are supported in a single request:
- Digital Property Search Report (DPSR) — a title search on the property
- CERSAI Search Report — checks security interests registered on the property
- Legal Due Diligence Report (LDDR) — a comprehensive legal opinion requiring document uploads by the lender
The service is asynchronous: reports are delivered to the lender's registered callback URL once ready. Six API endpoints cover the full lifecycle: report initiation, document upload, document status update, comment exchange, report status polling, and report download.
Who can use it?
Lenders and financial institutions onboarded to the ULI Platform who have subscribed to the TEAL Property Search service in the Developer Portal.
What are the prerequisites?
Complete all common platform prerequisites as described in Getting Started with ULI Platform APIs.
In addition, the following are specific to this service:
- The lender's callback URL must be registered with the ULI Platform during onboarding. DPSR, CERSAI, and LDDR reports are pushed to this URL when ready.
- An
x-sp-auth-token(JWT) must be provided so the platform can authenticate callbacks sent to the lender. - TEAL will provide a
query-idin the initiation response; this is required for subsequent document upload, status, and comment calls. - For SBI-specific integrations,
x-sp-lender-codeandx-sp-access-tokenheaders are additionally required. - Ensure the TEAL service is subscribed separately for Sandbox and Production in the Dev Portal.
What are the API endpoints?
| Service | Purpose | Sandbox URL | Production URL | Method |
|---|---|---|---|---|
propsearchteal | Initiate a DPSR, CERSAI, or LDDR report request | https://extgw.nonprod.rbihub.io/propsearchteal/1.4/en | https://extgw.api.rbihub.io/propsearchteal/1.4/en | POST |
propsearchtealdocupload | Upload a document requested by TEAL for LDDR generation | https://extgw.nonprod.rbihub.io/propsearchtealdocupload/1.4/en | https://extgw.api.rbihub.io/propsearchtealdocupload/1.4/en | POST |
propsearchtealdocstatus | Inform TEAL when a requested document is not available or waived | https://extgw.nonprod.rbihub.io/propsearchtealdocstatus/1.4/en | https://extgw.api.rbihub.io/propsearchtealdocstatus/1.4/en | POST |
propsearchtealcomment | Seek clarification on a LDDR document request from TEAL | https://extgw.nonprod.rbihub.io/propsearchtealcomment/1.4/en | https://extgw.api.rbihub.io/propsearchtealcomment/1.4/en | POST |
propsearchtealreportstatus | Poll for the current status of a requested report | https://extgw.nonprod.rbihub.io/propsearchtealreportstatus/1.0/en | https://extgw.api.rbihub.io/propsearchtealreportstatus/1.0/en | POST |
propsearchtealreportdownload | Download the report document using a file token from TEAL | https://extgw.nonprod.rbihub.io/propsearchtealreportdownload/1.0/en | https://extgw.api.rbihub.io/propsearchtealreportdownload/1.0/en | POST |
What headers must be sent?
The following headers apply to all endpoints. Additional headers are noted where applicable.
| Header | Description | Required |
|---|---|---|
Authorization | JWT Bearer token from the Authentication API | Mandatory |
client-id | Base64-encoded Client ID from onboarding | Mandatory |
provider | 114 for TEAL | Mandatory |
x-sp-auth-token | JWT token for authenticating callbacks to the lender (v1.3 onwards); not required for report status/download | Mandatory for initiation and doc endpoints |
query-id | ID returned in the initiation response; required for doc upload, doc status, and comment endpoints (v1.4 onwards) | Mandatory where applicable |
x-env-route | Set to /sb for Sandbox only | Sandbox only |
x-sp-lender-code | Lender code provided by TEAL — SBI-specific integrations only | SBI only |
x-sp-access-token | Encrypted secret key for SBI payload encryption — SBI-specific integrations only | SBI only |
api-key | Reserved for future use; optional | Optional |
What does the request body look like?
propsearchteal — Initiation request
{
"data": {
"applicant-details": { "name": "Applicant Name", "pan": "PANXXXXXX" },
"mortgager-details": { "name": "Mortgager Name" },
"property-details": {
"address": "Full property address",
"pincode": "560001",
"district": "Bengaluru Urban",
"state": "Karnataka",
"type": "Apartment"
},
"reference-data": { "case-number": "LAN/KA/2246", "lender-code": "BANK_QP286" },
"reports-requested": ["Digital Property Search Report", "CERSAI Search Report", "Legal Due Diligence Report"]
},
"meta": { "ts": "2023-01-03T21:10:23+05:30", "ver": "1.3", "txncode": "KA01" },
"hmac": "SHA-256 hash of key 'data'"
}
| Field | Required | Description |
|---|---|---|
applicant-details.name | Yes | Applicant name (1–256 characters) |
applicant-details.pan | No | Applicant PAN |
property-details.address | Yes | Full address (1–2048 characters) |
property-details.pincode | Yes | Property pincode |
property-details.district | Yes | District name |
property-details.state | Yes | State name or code |
property-details.type | No | Property type, e.g., Apartment, Farmland |
reference-data.lender-code | Yes | Lender identifier code |
reports-requested | Yes | Array containing one or more of: Digital Property Search Report, CERSAI Search Report, Legal Due Diligence Report |
hmac | Yes | SHA-256 hash of the data key value |
propsearchtealdocupload — Document upload
Pass data.id (document ID from the TEAL callback), data.name (document name), data.file-type (e.g., application/pdf), and data.base64 (base64-encoded file content, max 200 MB).
propsearchtealdocstatus — Document status
Pass data.id (document ID), data.status (Not Available or Waived), and an optional data.remark.
propsearchtealcomment — Comment
Pass data.comment with your clarification text.
What does the response contain?
On successful initiation, the response includes a query_id that must be stored for subsequent document and status calls. Reports are delivered asynchronously to the lender's callback URL. The callback payload includes:
| Field | Description |
|---|---|
fileLink | Downloadable file URL for the report (DPSR/CERSAI) |
fileSizeMb | File size in megabytes |
query_id | Transaction query identifier |
reportName | Name of the report delivered |
status | Report fulfilment status (e.g., Fulfilled) |
txncode | Lender's original transaction code |
updateTimestamp | Timestamp of the update |
The platform retries failed callback deliveries up to three times.
What are the error codes?
Refer to the Latest Platform Error Code document on the Dev Portal for the full list of error values applicable to this service.
Who do I contact for support?
Write to support@rbihub.in with the following details:
- Subject: Property Search API Error (Teal)
- Service Name: Property Search (Teal)
- Environment: Sandbox / Production
- Service Provider code: 114 (TEAL)
- Request Payload (headers and body)
- Error Code and Error Message received
- Screenshot or log of the error
- Prerequisites status: IP Whitelisting, URL Whitelisting, Service Subscription, Token Generation
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article