---
title: "Retrieve LIDAR Status"
method: GET
path: "/tenants/{tenant_id}/designs/{design_id}/lidar_status"
tags: ["LIDAR Status"]
---

# Retrieve LIDAR Status

`GET /tenants/{tenant_id}/designs/{design_id}/lidar_status`

## Request

- Base URL: `https://api-sandbox.aurorasolar.com`
- URL: `https://api-sandbox.aurorasolar.com/tenants/{tenant_id}/designs/{design_id}/lidar_status`
- Auth: HTTP bearer

Report whether the elevation (LIDAR/DSM) data selected for a design is out of date
relative to the imagery selected for that design, along with the capture date of
each and the imagery resolution.

---

Use this before running AI Roof to predict output quality: a design whose elevation
data is out of date relative to its imagery is likely to produce a poorer roof model.

Note that "out of date" is a comparison *between the two sources*, not a judgement
about whether either is current in absolute terms. Two sources captured at the same
time agree with each other even if both are old, so read `capture_date` alongside it.

## Path parameters

- `tenant_id` string, uuid, required
- `design_id` string, uuid, required

## Response `200`

The current LIDAR status for the design.

- object
  - `lidar_status` object, required
    - `out_of_date` object, required
      - `status` 'up_to_date' | 'out_of_date' | 'unavailable', required: Whether the elevation data is out of date relative to the imagery currently selected for this design. `up_to_date` and `out_of_date` are verdicts; `unavailable` means no verdict could be produced, and `reason` says why.
      - `reason` 'lidar_data_unavailable' | 'computation_failed', nullable, required: Why no verdict is available. Null unless `status` is `unavailable`. `lidar_data_unavailable`: the imagery or LIDAR for this design could not be identified or is not yet usable, so there is nothing to compare. `computation_failed`: the comparison could not be completed; retrying may succeed.
    - `imagery` object, required
      - `capture_date` string, nullable, required: Calendar date the imagery was captured, when reported by the provider.
      - `resolution` number, nullable, required: Imagery resolution in centimetres per pixel, when reported by the provider.
    - `lidar` object, required
      - `capture_date` string, nullable, required: Calendar date the elevation capture began, when available. For Aurora LIDAR flights spanning multiple days this is the start of the window; the end date is not returned. Resolution is not exposed for elevation data because the stored point spacing may have been downsampled.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found

## Changes

- **2026-11-03** `97a7ad8a993a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/aurorasolar/apis/sync-api/changes/tenants/:tenant_id/designs/:design_id/lidar_status/get.md)

---

[API](https://skmtc.dev/aurorasolar/apis/sync-api.md) - [All operations](https://skmtc.dev/aurorasolar/apis/sync-api/llms.txt) - [OpenAPI document](https://skmtc.dev/aurorasolar/apis/sync-api/revisions/97a7ad8a993a?raw)