> ## Documentation Index > Fetch the complete documentation index at: https://developer.hayinsights.com/llms.txt > Use this file to discover all available pages before exploring further. # List priced road segments > Priced road segments for a country, with residential, commercial and production prices across value-position tiers. Filter by land-use `type`, `area`, `ward_id` or a free-text search, and cap the result count with `limit`. Data is available for `vn`. ## OpenAPI ````yaml /openapi.yaml get /openapi/v1/real-estate/{country}/land-prices openapi: 3.1.0 info: title: HayInsights Open API version: 0.1.0 description: > Programmatic access to the **HayInsights** financial-data hub — commodities, crypto, ETF, FX, macroeconomic and real-estate datasets, served from a single API surface under `/openapi/v1/*`. This specification is the **single source of truth** for the public API surface — shared by SDK codegen, the reference docs, and (later) the mock server / contract tests. ## Authentication Every request must carry your API key in the `X-API-Key` header. There is a single authentication tier — no request signing. Create and manage keys in the HayInsights dashboard (Account → API keys). See **Authentication**. ## Plans & quota Access to each data domain and your request quota are governed by the subscription plan attached to your key. Each endpoint consumes a **weighted** amount of your per-minute quota; every response carries `X-RateLimit-*` headers. See **Rate limits** and **Plans & features**. contact: {} servers: - url: https://api.hayinsights.com description: Production security: - HayInsightsApiKey: [] tags: - name: Commodities description: >- Spot prices, top movers, gold–DXY correlation and historical series for energy, metals and agricultural commodities. - name: Crypto description: >- Crypto market overview, dominance, bubble map, on-chain and derivatives metrics. - name: ETF description: >- Exchange-traded fund listings, performance & net-flow rankings, heatmap, holdings, NAV growth and fund composition. - name: FX description: >- Foreign-exchange summary, live table, 90-day correlation matrix and the emerging-market stress monitor. - name: Macro description: >- Macroeconomic indicators — GDP, CPI/PCE, exchange rates, population, central-government debt and policy rates / bond yields. - name: Real Estate description: >- Real-estate statistics, land prices, administrative geography (provinces / wards) and choropleth GeoJSON, by country. paths: /openapi/v1/real-estate/{country}/land-prices: get: tags: - Real Estate summary: List priced road segments description: > Priced road segments for a country, with residential, commercial and production prices across value-position tiers. Filter by land-use `type`, `area`, `ward_id` or a free-text search, and cap the result count with `limit`. Data is available for `vn`. operationId: realEstateLandPrices parameters: - name: country in: path required: true description: Country code, lowercase. schema: type: string example: vn - name: type in: query required: false description: | Filter by land-use type. | Value | Description | | --- | --- | | `residential` | Residential land | | `commercial` | Commercial land | | `production` | Production / industrial land | schema: type: string enum: - residential - commercial - production - name: area in: query required: false description: | Filter by area / land-value zone. | Value | Description | | --- | --- | | `I` | Value zone I (highest) | | `II` | Value zone II | | `III` | Value zone III | | `IV` | Value zone IV (lowest) | schema: type: string enum: - I - II - III - IV - name: ward_id in: query required: false description: Filter by ward identifier. schema: type: integer example: 169 - name: q in: query required: false description: Free-text search on road / ward name. schema: type: string example: Hai Bà Trưng - name: limit in: query required: false description: Maximum number of segments to return. schema: type: integer example: 100 responses: '200': description: List of priced road segments. content: application/json: schema: $ref: '#/components/schemas/RealEstateLandPricesResponse' example: success: true statusCode: 200 data: - wardId: 169 wardName: Khu vực 1 area: Khu vực 1 roadName: Nhà Thờ segmentFrom: Đầu đường segmentTo: Cuối đường priceResidentialVt1: 702194 priceResidentialVt2: 316389 priceResidentialVt3: 229626 priceResidentialVt4: 196388 priceCommercialVt1: null priceCommercialVt2: null priceCommercialVt3: null priceCommercialVt4: null priceProductionVt1: null priceProductionVt2: null priceProductionVt3: null priceProductionVt4: null unit: k_vnd year: 2026 month: 1 meta: timestamp: '2026-06-19T08:54:29.621Z' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' '500': $ref: '#/components/responses/InternalError' components: schemas: RealEstateLandPricesResponse: allOf: - $ref: '#/components/schemas/EnvelopeBase' - type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/RealEstateLandPrice' EnvelopeBase: type: object description: > Standard success envelope shared by every endpoint. Each operation's response wrapper extends this (via `allOf`) and adds a typed `data` property. required: - success - statusCode properties: success: type: boolean const: true description: Always `true` for a successful response. example: true statusCode: type: integer description: Mirrors the HTTP status code. example: 200 meta: $ref: '#/components/schemas/Meta' RealEstateLandPrice: type: object description: > A single priced road segment. Each segment carries residential, commercial and production prices across four value-position tiers (`Vt1..4`, frontage → rear). Tiers or price types that do not apply to a segment are `null`. required: - wardId - wardName - area - roadName - unit - year - month properties: wardId: type: integer description: Ward identifier the segment belongs to. example: 169 wardName: type: string description: Ward name. example: Khu vực 1 area: type: string description: Area / land-value zone label (localized). example: Khu vực 1 roadName: type: - string - 'null' description: Road name. example: Nhà Thờ segmentFrom: type: - string - 'null' description: Start of the priced segment. example: Đầu đường segmentTo: type: - string - 'null' description: End of the priced segment. example: Cuối đường priceResidentialVt1: type: - number - 'null' description: Residential price, value-position tier 1. example: 702194 priceResidentialVt2: type: - number - 'null' description: Residential price, value-position tier 2. example: 316389 priceResidentialVt3: type: - number - 'null' description: Residential price, value-position tier 3. example: 229626 priceResidentialVt4: type: - number - 'null' description: Residential price, value-position tier 4. example: 196388 priceCommercialVt1: type: - number - 'null' description: Commercial price, value-position tier 1. example: null priceCommercialVt2: type: - number - 'null' description: Commercial price, value-position tier 2. example: null priceCommercialVt3: type: - number - 'null' description: Commercial price, value-position tier 3. example: null priceCommercialVt4: type: - number - 'null' description: Commercial price, value-position tier 4. example: null priceProductionVt1: type: - number - 'null' description: Production / manufacturing price, value-position tier 1. example: null priceProductionVt2: type: - number - 'null' description: Production / manufacturing price, value-position tier 2. example: null priceProductionVt3: type: - number - 'null' description: Production / manufacturing price, value-position tier 3. example: null priceProductionVt4: type: - number - 'null' description: Production / manufacturing price, value-position tier 4. example: null unit: type: string description: Price unit. `k_vnd` means thousands of VND per square metre. example: k_vnd year: type: integer description: Year the price schedule applies to. example: 2026 month: type: integer description: Month the price schedule applies to. example: 1 ErrorBody: type: object description: Standard error envelope returned for every 4xx / 5xx response. required: - success - statusCode - error properties: success: type: boolean const: false description: Always `false` for an error response. example: false statusCode: type: integer description: Mirrors the HTTP status code. example: 401 error: $ref: '#/components/schemas/ErrorDetail' meta: $ref: '#/components/schemas/Meta' Meta: type: object description: >- Response metadata. Always present; `timestamp` is the server time the response was generated. required: - timestamp properties: timestamp: type: string format: date-time description: Server time when the response was generated (ISO 8601). example: '2026-06-19T08:31:59.478Z' additionalProperties: true ErrorDetail: type: object description: Error detail object carried under `error` in the error envelope. required: - code - message properties: code: type: string description: > Machine-readable error code. Specific for authentication / quota errors (e.g. `API_KEY_REQUIRED`, `API_KEY_INVALID`, `FEATURE_NOT_IN_PLAN`, `RATE_LIMIT_EXCEEDED`). For validation (400) and not-found (404) the code is currently `INTERNAL_ERROR` and the HTTP status carries the semantics. example: API_KEY_INVALID message: description: Human-readable message, or a list of validation messages (400). oneOf: - type: string - type: array items: type: string example: Invalid API key responses: BadRequest: description: >- Invalid or missing parameter — bad enum, range, format, or a missing required query parameter. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 400 error: code: INTERNAL_ERROR message: - >- Invalid type parameter. Must be "gdp", "cpi", "pce", or "import-export" - Type parameter is required meta: error: Bad Request statusCode: 400 timestamp: '2026-06-19T08:34:08.081Z' Unauthorized: description: >- Missing, invalid, disabled or expired API key. Send a valid key in the `X-API-Key` header. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 401 error: code: API_KEY_INVALID message: Invalid API key meta: timestamp: '2026-06-19T08:34:08.023Z' Forbidden: description: >- Your subscription plan does not include this data feature, or your key's scope denies it. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 403 error: code: FEATURE_NOT_IN_PLAN message: Your plan does not include this feature meta: timestamp: '2026-06-19T08:34:08.100Z' NotFound: description: The requested resource was not found. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 404 error: code: INTERNAL_ERROR message: Commodity 'zzz-nope' not found meta: error: Not Found statusCode: 404 timestamp: '2026-06-19T08:34:08.205Z' RateLimited: description: > Rate limit exceeded — you have consumed your plan's per-minute weight budget. Wait until `X-RateLimit-Reset` (or `Retry-After` seconds) then retry. headers: X-RateLimit-Limit: $ref: '#/components/headers/XRateLimitLimit' X-RateLimit-Remaining: $ref: '#/components/headers/XRateLimitRemaining' X-RateLimit-Reset: $ref: '#/components/headers/XRateLimitReset' X-RateLimit-Weight-Used: $ref: '#/components/headers/XRateLimitWeightUsed' Retry-After: $ref: '#/components/headers/RetryAfter' content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 429 error: code: RATE_LIMIT_EXCEEDED message: Rate limit exceeded meta: timestamp: '2026-06-19T08:34:09.000Z' InternalError: description: Unexpected server error. Retry after a short exponential backoff. content: application/json: schema: $ref: '#/components/schemas/ErrorBody' example: success: false statusCode: 500 error: code: INTERNAL_ERROR message: Internal server error meta: timestamp: '2026-06-19T08:34:10.000Z' headers: XRateLimitLimit: description: Your plan's request-weight budget per 1-minute window. schema: type: integer example: 1000 XRateLimitRemaining: description: Remaining request weight in the current 1-minute window. schema: type: integer example: 997 XRateLimitReset: description: Unix timestamp (seconds) when the current rate-limit window resets. schema: type: integer format: int64 example: 1781857979 XRateLimitWeightUsed: description: Request weight consumed by this call (see each endpoint's weight). schema: type: integer example: 3 RetryAfter: description: Seconds to wait before retrying. Present on 429 responses. schema: type: integer example: 30 securitySchemes: HayInsightsApiKey: type: apiKey in: header name: X-API-Key description: > Your HayInsights API key (prefixed `apk_`). Create and manage keys in the HayInsights dashboard (Account → API keys). Send it in the `X-API-Key` header on **every** request to `/openapi/v1/*`. Which data domains you may access and your request quota are both governed by the subscription plan attached to the key — see the **Plans & features** and **Rate limits** guides. ````