---
title: "Get a taxonomy run"
method: GET
path: "/v1/taxonomy/runs/{run_id}"
tags: ["Taxonomy"]
---

# Get a taxonomy run

`GET /v1/taxonomy/runs/{run_id}`

Returns a single taxonomy run by ID, scoped to the tenant. Returns 404 if the run does not belong to the tenant.

## Path parameters

- `run_id` string, uuid, required

## Query parameters

- `tenant_id` string, required

## Response `200`

The taxonomy run

- TaxonomyRunData — A persisted taxonomy generation run.
  - `id` string, uuid, required
  - `scope_type` 'field' | 'directory', required — Taxonomy input scope. `field` covers one (source_type, source_id, field_id) field scope. `directory` covers all text feedback records for the tenant/directory and must not include source_type, source_id, or field_id.
  - `tenant_id` string, required
  - `source_type` string, required
  - `source_id` string, required — Empty string is the canonical "no source" bucket.
  - `field_id` string, required
  - `field_label` string — Human-readable field label; absent when unknown.
  - `status` 'pending' | 'running' | 'succeeded' | 'failed' | 'canceled', required — Lifecycle state of a taxonomy run. Allowed transitions are pending -> running|failed|canceled and running -> succeeded|failed|canceled.
  - `params` object — Opaque run parameters recorded by Hub.
  - `metrics` object — Opaque run metrics recorded by the taxonomy service.
  - `record_count` integer, required
  - `embedding_count` integer, required
  - `cluster_count` integer, required
  - `node_count` integer, required
  - `error` string — Sanitized failure message; present on failed runs.
  - `error_code` 'insufficient_data' | 'service_unavailable' | 'generation_failed' | 'invalid_output' | 'internal_error' — Machine-readable reason a taxonomy run failed or a prerequisite was not met.
  - `started_at` string, date-time
  - `finished_at` string, date-time
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required

## Other responses

- `400` — Bad Request (e.g. invalid run_id or missing/invalid tenant_id)
- `401` — Unauthorized (missing or invalid API key)
- `404` — Not Found – no run with this ID for the tenant.
- `default` — Error

---

[API](https://skmtc.net/formbricks/apis/formbricks-hub-api.md) · [All operations](https://skmtc.net/formbricks/apis/formbricks-hub-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/formbricks/formbricks-hub-api/revisions/8d06d9728138/schema)