---
title: "Warehouse types that have a live engine driver."
method: GET
path: "/v1/connections/drivers"
tags: ["connections"]
---

# Warehouse types that have a live engine driver.

`GET /v1/connections/drivers`

## Request

- Base URL: `http://localhost:8080`
- URL: `http://localhost:8080/v1/connections/drivers`
- Auth: one of:
  - API key in cookie `dvt_session`
  - HTTP bearer

Returns the warehouse `type` values that have a registered engine driver and can
therefore run a query today (the driver registry, ADR-0012). The UI uses this to show
real availability rather than a static list — a newly shipped driver appears here
automatically. Admin or above.

`engineReachable` reports whether the engine actually answered. When the engine is
unreachable or errors, the API still returns a conservative fallback (the
always-registered `postgres` driver) so the surface renders, but sets
`engineReachable: false` so the UI can surface an "engine unreachable" / degraded
state rather than presenting the fallback as the complete, real catalog (DVT-148).

## Response `200`

The queryable warehouse types, and whether the engine answered.

- object
  - `data` object, required
    - `queryableTypes` string[], required: data_sources.type values that have a registered driver.
    - `engineReachable` boolean, required: True when the engine answered the driver-registry query. False means the list is a conservative fallback and the engine is unreachable / degraded — surface that to the user, don't treat it as the real catalog.

## Other responses

- `401`: Missing, invalid, or expired session.
- `403`: The caller's role does not permit this action.

---

[API](https://skmtc.dev/dvt/apis/dvt-rest-api.md) · [All operations](https://skmtc.dev/dvt/apis/dvt-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dvt/apis/dvt-rest-api/revisions/00016f504165?raw)