Ownership and attribution
Nestscout does not own the listings. Keep each record’s original source visible and link to its sourceUrl whenever the record is displayed.
Quick start
API keys are issued manually and can be revoked. Send the key as a Bearer token; never include it in a query string.
RequestFirst page
curl --fail-with-body \
--request GET \
--url 'https://nestscout.in/api/v1/listings' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer YOUR_KEY'Request a key at api@nestscout.in. Mention what you are building and whether its output will be public.
Server-side requests
Cross-origin browser requests are not enabled. Keep API keys in server-side code and store retrieved records in your own datastore.
Endpoint
GET /api/v1/listings
Returns up to 500 records in stable primary-key order.
Response200 OK · application/json
{
"apiVersion": "1",
"count": 500,
"nextCursor": "WyJob3VzaW5nIiwiMTIzNDU2Il0",
"next": "https://nestscout.in/api/v1/listings?cursor=…",
"data": [{
"id": "housing:123456",
"source": "housing",
"sourceId": "123456",
"sourceUrl": "https://housing.com/…",
"deal": "RENT",
"title": "2 BHK in Koramangala",
"propertyType": "Apartment",
"bhk": 2,
"price": 28000,
"sqft": 1150,
"locality": "Koramangala",
"city": "Bengaluru",
"firstSeen": "2026-07-10T06:41:00+00:00"
}]
}The only accepted query parameter is cursor. Locality, price, BHK, radius, sort, limit and offset parameters are not supported.
Pagination
Follow next, or pass nextCursor back as ?cursor=…. Stop when both are null. Do not decode, edit or manufacture cursors.
RequestNext page
curl --fail-with-body \
--request GET \
--url 'https://nestscout.in/api/v1/listings?cursor=WyJob3VzaW5nIiwiMTIzNDU2Il0' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer YOUR_KEY'The feed is live rather than a transactional export. If an index refresh completes while you are paging, additions or removals may cross the cursor boundary. For a public mirror, complete a fresh pass and reconcile it with your stored copy.
Fields
Missing source data is returned as null. Do not infer that a null field means “no”; it usually means the source did not say.
| Fields | Meaning |
|---|---|
id, sourceId | Nestscout’s stable composite key and the identifier supplied by the source. |
source, sourceUrl | Required provenance. The source URL is the canonical place to verify and attribute the listing. |
deal, propertyType | The advertised transaction and property category. |
title | Title published by the source, where available. |
bhk, bhkRaw, bedrooms, bathrooms | Normalized bedroom count alongside the source’s original label. |
sqft, sqftUnit | Advertised area and unit. |
price, priceDisplay, deposit, maintenance | Normalized monthly rent where safe, plus source-presented money fields. |
furnishing, parking, negotiable | Basic property terms as supplied. |
leaseType, isLease, shared, flatmate | Signals distinguishing conventional rentals, lease arrangements and shared homes. |
tenantType, preferredGender, petFriendly, availableFrom | Occupancy preferences. Treat these as unverified source claims. |
locality, sublocality, society, city | Source-provided location labels. |
lat, lon | Coordinates where available; some sources provide approximate centroids. |
verified | The source’s verification signal, not an independent Nestscout guarantee. |
postedDate, lastUpdated, firstSeen | Source dates where available and when Nestscout first indexed the record. |
Images are not included.
With its current resources, Nestscout cannot operate the temporary-URL generation and validation infrastructure required for image access at API scale.
Errors
| Status | Meaning |
|---|---|
400 | Unsupported parameter or malformed cursor. |
401 | Bearer key missing, invalid or revoked. |
404 | Endpoint or API version does not exist. |
405 | Only GET and HEAD are supported. |
429 | The key or client is sending requests too aggressively. |
502, 503 | Temporary upstream or configuration failure. Back off; do not retry in a tight loop. |
Usage guidelines
Use the API as a periodically refreshed feed. Cache each completed sync and serve application traffic from your own infrastructure.
Sync at most once per six hoursThe underlying index changes on roughly that cadence. Faster polling only retrieves cached copies.
Make requests sequentiallyFollow one cursor at a time and stay at or below one request per second.
Store the responseFilter, search, rank and count locally. Never repeat a call for each visitor or UI interaction.
Respect cached responsesDo not add cache-busting parameters. Use ordinary exponential backoff after failures.
Reference ends here
Usage & legal
The following sections contain the ownership, attribution and usage conditions presented before the documentation.
Attribution and ownership
Nestscout does not own the listings. Listing text and facts originate with the person or organization that posted them and the platform identified by source. Availability through this API does not transfer copyright, database rights or any other licence from those parties.
Whenever you display a record, visibly name the original source and link to its sourceUrl. Do not remove provenance or imply that Nestscout verified, licensed or owns the listing.
Attribution examplesDisplay text
Source: Housing.com ↗
Original listing: Housing.com · Indexed via NestscoutYou are responsible for checking and complying with the original source’s terms before retaining, republishing or commercially exploiting its data.
If your product will be public
Do not wire visitor traffic directly to Nestscout. A public app, bot, website or hosted dataset must ingest periodically into infrastructure you control.
- Keep the API key server-side and out of repositories, browser bundles, mobile apps and shared notebooks.
- Serve searches and pages from your own database or cache. One user action must not become one Nestscout API request.
- Do not proxy the endpoint under your own domain, redistribute keys, or offer a substantially identical bulk-feed API.
- Preserve source attribution and reconcile removals during each full sync.
- Contact api@nestscout.in before launch so usage and source obligations are clear.
Conditions of use
By using a key, you agree to:
- Use the feed for lawful personal, research or expressly agreed purposes.
- Credit and link to each record’s original source; never claim Nestscout owns or licenses the underlying listing.
- Not harvest contact details, facilitate spam, evade source access controls, or use the feed for surveillance or unlawful discrimination.
- Not sell access to the raw feed, publish a bulk clone, share a key, or operate Nestscout as the live backend for another service.
- Respect removal and correction requests and the terms of every original source.
- Accept that the feed may be incomplete, delayed, duplicated, incorrect or withdrawn without notice. There is no service-level guarantee.
Keys may be limited or revoked to protect Nestscout, data subjects, original sources or operating costs. Version-breaking changes will use a new URL where practical.