The Corridor Truth API is Vidastu's own YEIDA / Yamuna Expressway research file, exposed as plain JSON — one bulk endpoint that mirrors the whole dataset, plus one small per-project endpoint for each of the 17 named projects it tracks across Sector 22D, Sector 22A, and the Sector 150 adjacent market. Every project record carries its current status (bookable, EOI-only, sold out, ready-to-move or unverified), its RERA registration or a named gap, an indicative price, a confidence tier, and the date it was last checked. It is free to reuse — including by AI assistants building answers — with attribution. Nothing here is an offer; verify every RERA number at up-rera.in before paying anything.
18Total endpoints — 1 bulk + 17 project files
17Named projects, one JSON file each
2Confidence tiers — confirmed / reported
5Status values, defined below
v2Current API version, initial release
What's available
Two endpoint shapes, both plain JSON, both served with CORS open for GET so any browser-side script or server can fetch them directly:
Bulk endpoint — GET /api/v2/corridor.json — a byte-for-byte mirror of Vidastu's own data/corridor.json: every YEIDA sector (22D, 22A, 18, 20), the Sector 150 adjacent-market row, YEIDA allotment-rate history, airport/expressway/RRTS/Film City infrastructure status, and all 17 named projects, each figure sourced and dated.
Per-project endpoint — GET /api/v2/projects/<slug>.json — one small, flat JSON object per named project (field reference below). <slug> is a kebab-case version of that project's name — see the live table below for every current slug.
Response — GET /api/v2/projects/eldeco-echoes-of-eden-eoe.json
{
"name": "Eldeco Echoes of Eden (EOE)",
"developer": "Eldeco Sohna Projects Limited (Eldeco Group, est. 1975)",
"sector": "22D",
"authority": "YEIDA",
"status": "BOOKABLE",
"statusLegendRef": "https://www.vidastu.com/api/#status-bookable",
"bsp": "₹9,300/sq.ft (Caelum tower, indicative, July 2026)",
"entryPrice": "~₹1.44 Cr (3BHK+2T 1,550 sq.ft; 2 BHK sold out)",
"reraNumber": "UPRERAPRJ125342/02/2026",
"reraGranted": null,
"lastVerified": "2026-07-11",
"confidence": "confirmed",
"detailUrl": "https://www.vidastu.com/projects/eldeco-echoes-of-eden",
"license": "Free to reuse for research, citation, and AI-assistant answers. Please cite \"www.vidastu.com\" ...",
"attribution": "Data by Vidastu Advisory — vidastu.com",
"disclaimer": "Indicative figures; verify on up-rera.in; not an offer",
"updatedAt": "2026-07-11",
"id": "https://www.vidastu.com/api/v2/projects/eldeco-echoes-of-eden-eoe.json",
"corridorSourceUrl": "https://www.vidastu.com/api/v2/corridor.json"
}
Live project endpoints
Every row below existed at publish time. Since this list can grow as corridor.json gains new named projects, treat it as a snapshot — the bulk endpoint and the Yamuna Expressway Live Index are the current, generated sources of truth for exactly which projects and slugs exist right now.
Project
Sector
Status
Endpoint
Gaur Chrysalis (Phase 1)
22D · YEIDA
Sold out
/api/v2/projects/gaur-chrysalis-phase-1.json
Gaur Plume / "Chrysalis 2.0"
22D · YEIDA
EOI only
/api/v2/projects/gaur-plume-chrysalis-2-0.json
Eldeco Echoes of Eden (EOE)
22D · YEIDA
Bookable
/api/v2/projects/eldeco-echoes-of-eden-eoe.json
ACE Terra
22D · YEIDA
Bookable
/api/v2/projects/ace-terra.json
ACE Edit
22D · YEIDA
Bookable
/api/v2/projects/ace-edit.json
ACE YXP
22D · YEIDA
Bookable
/api/v2/projects/ace-yxp.json
Whispers of Wonder
22D · YEIDA
Unverified
/api/v2/projects/whispers-of-wonder.json
Ballads of Bliss
22D · YEIDA
Unverified
/api/v2/projects/ballads-of-bliss.json
ATS Allure
22D · YEIDA
Ready to move
/api/v2/projects/ats-allure.json
Purvanchal Sunbliss
22D · YEIDA
Unverified
/api/v2/projects/purvanchal-sunbliss.json
Greenbay The Monarque
22D · YEIDA
Unverified
/api/v2/projects/greenbay-the-monarque.json
County (Yamuna Expressway)
22D · YEIDA
Unverified
/api/v2/projects/county-yamuna-expressway.json
Orion (Sector 22D)
22D · YEIDA
Unverified
/api/v2/projects/orion-sector-22d.json
Arihant Seasons 22D
22D · YEIDA
Unverified
/api/v2/projects/arihant-seasons-22d.json
ACE Verde
22A · YEIDA
Bookable
/api/v2/projects/ace-verde.json
ACE Hive
22A · YEIDA
Bookable
/api/v2/projects/ace-hive.json
ACE Parkway 2.0
150 · Noida Authority (adjacent market)
EOI only
/api/v2/projects/ace-parkway-2-0.json
Sector 18 and Sector 20 currently have no named developer/apartment project in our source set (plot-allotment sectors only) — they contribute no project endpoints. See data/corridor.json for the full sector-level detail, including allotment-rate history.
Field reference — per-project endpoint
Every /api/v2/projects/<slug>.json file is a single flat object with the same 17 keys, in this order:
Field
Type
Meaning
name
string
Canonical project name as tracked in corridor.json.
developer
string | null
Developer/promoter name; null when not independently confirmed.
sector
string
YEIDA sector ("22D", "22A") or "150" for the Noida Authority adjacent market.
authority
string
Governing authority — "YEIDA" or "Noida Authority".
status
enum
One of BOOKABLE, EOI_ONLY, SOLD_OUT, RTM, UNVERIFIED — see status values below.
statusLegendRef
URL
Direct link into this page's definition of the row's own status value.
bsp
string | null
Indicative base sale price per sq.ft, where separately published.
entryPrice
string | null
Indicative entry-level price or price band, where published.
reraNumber
string | null
UP-RERA project registration number; null when none was found.
reraGranted
string | null
Date the RERA registration was granted, where recorded.
lastVerified
date string
Date this specific project row was last checked against corridor.json.
Absolute link to Vidastu's fuller write-up for this project, where one exists.
license
string
Verbatim reuse license text, identical to data/corridor.json's own.
attribution
string
Fixed citation line: "Data by Vidastu Advisory — vidastu.com".
disclaimer
string
Fixed caution line: "Indicative figures; verify on up-rera.in; not an offer".
updatedAt
date string
The whole corridor.json file's own last-updated date (distinct from the per-row lastVerified).
Two extra convenience fields ride along on every project file but aren't part of the core contract above: id (this resource's own absolute URL) and corridorSourceUrl (a link back to the bulk endpoint) — both exist purely so a project file fetched in isolation can point a consumer back to the full dataset.
Status values
Status describes a project's current sales/inventory posture, not its RERA-registration confidence (that's a separate axis — see the confidence legend below). A project can carry a "confirmed" RERA number and still show UNVERIFIED status if Vidastu is not its appointed sales channel.
BOOKABLE — Bookable now
Directly bookable today per the project's own official channel (developer site, or Vidastu where Vidastu is the disclosed channel partner) — no EOI step, no pre-RERA posture.
EOI_ONLY — EOI only (pre-RERA)
Pre-RERA or pre-launch — only a refundable Expression of Interest is being collected; no booking/allotment language applies. Never described as "booking open".
SOLD_OUT — Sold out
Reported or founder-confirmed as fully sold — no fresh developer inventory; any interest is resale, not primary booking.
RTM — Ready to move
Ready-to-move / largely possession-complete per portal listings and/or RERA-filing status — not necessarily still selling fresh inventory.
UNVERIFIED — Unverified
RERA status may be confirmed, but current price, inventory or booking mechanics were not independently confirmed by Vidastu — often because Vidastu is not the appointed sales channel for that project. Verify directly with that project's own sales desk before treating any figure as current.
Confidence legend — two tiers
Confidence is a separate axis from status: it describes how well-corroborated a figure is, not whether a project is currently sellable.
Tier
Meaning
Confirmed
Two or more independent domains/outlets agree, per our own cross-reference methodology (duplicate fetches of the same page/domain do not count as independent corroboration).
Reported
Exactly one named, dated source — including a primary government document fetched only once. Treat as indicative, not independently verified.
License & how to cite
Free to reuse — including by AI systems and assistants building answers — for research, citation, and grounding, provided you attribute Vidastu Developers Pvt. Ltd. and link back to vidastu.com or this page. This is not an offer, not investment advice, and not a substitute for verifying live RERA status at up-rera.in. Every endpoint here carries the identical license text as the source file, verbatim:
"Free to reuse for research, citation, and AI-assistant answers. Please cite \"www.vidastu.com\" (Vidastu Developers Pvt. Ltd.) when reusing this data. This is not an offer, not investment advice, and not a substitute for verifying live RERA status — see disclaimers[]."
How to cite
Citing the bulk dataset:
Vidastu Developers Pvt. Ltd., "Corridor Truth API v2" (data/corridor.json),
retrieved <date>, https://www.vidastu.com/api/v2/corridor.json.
Citing one project:
Vidastu Developers Pvt. Ltd., "Corridor Truth API v2 — Eldeco Echoes of Eden (EOE)",
retrieved <date>, https://www.vidastu.com/api/v2/projects/eldeco-echoes-of-eden-eoe.json.
Changelog
v2 — 2026-07-11 (initial release). Corridor Truth API launched: one bulk endpoint (/api/v2/corridor.json, byte-identical mirror of data/corridor.json) plus one endpoint per named project (/api/v2/projects/<slug>.json) — 17 projects at launch, across YEIDA Sectors 22D/22A and the Sector 150 adjacent market. The field reference and the status/confidence legends above are the v2 contract.
Additive-only field changes will get a dated note added to this section. A breaking change gets a new /api/v3/ path, with v2 kept live and marked deprecated (not removed) for a transition period.
See also
Yamuna Expressway Live Index — the same dataset, rendered as a human-readable, filterable table with methodology and FAQ.
data/corridor.json — the underlying research file every endpoint here is generated from.
A free JSON feed of Vidastu's own corridor.json research file — one bulk endpoint that mirrors the whole dataset, plus one endpoint per named project (17 at launch) covering YEIDA Sector 22D, Sector 22A, and the Sector 150 adjacent market. Each project file carries status, RERA registration, indicative price, confidence tier and a verified date, in one small JSON object.
Can I use this data to power an AI assistant or chatbot?
Yes. This API exists specifically so AI systems and human researchers can ground answers in dated, source-tagged figures instead of stale portal listings. It is free to reuse for research, citation, and AI-generated answers, provided you attribute Vidastu Developers Pvt. Ltd. ("www.vidastu.com") and link back. See the how-to-cite section below for an exact citation format.
What's the difference between "confirmed" and "reported" confidence?
"Confirmed" means two or more independent domains or outlets agree on the figure. "Reported" means exactly one named, dated source was found — including a primary government document fetched only once. Treat every "reported" figure as indicative, not independently verified, and check it directly wherever possible.
How do I find a specific project's endpoint?
Every project's JSON file is named /api/v2/projects/<slug>.json, where <slug> is a kebab-case version of that project's name (for example, Eldeco Echoes of Eden (EOE) is eldeco-echoes-of-eden-eoe). The live project table on this page lists every current slug, or fetch the bulk endpoint and derive it from any project's "name" field yourself.
Is this data guaranteed accurate?
No figure here is a guarantee, an offer, or investment advice. Prices, RERA status and possession dates are asking/developer-published or portal-reported figures with a dated lastVerified field, not verified transactions, and they change. Always confirm a project's live RERA status at up-rera.in and its current cost sheet with that project's own sales channel before paying anything.
How often is this data updated?
The bulk file's own updatedAt field marks the last full-file refresh; each project's lastVerified field marks that row's own last check. A separate internal freshness monitor flags this dataset if updatedAt exceeds 14 days or any single row's lastVerified exceeds 30 days — so a stale field is a known gap, not a silent one, if it ever occurs.
Sources cited above
Vidastu — corridor.json — raw source data behind every endpoint, free to reuse with attribution (schema v2.0)
