---
title: "List serving spec fields and how each may be changed (platform admin)"
method: GET
path: "/v1/admin/inference/serving/spec-fields"
tags: ["Internal"]
---

# List serving spec fields and how each may be changed (platform admin)

`GET /v1/admin/inference/serving/spec-fields`

The server's classification of every deployment spec field: structural (rejected everywhere), routing (PATCH), sizing (/scale), or replica (a blue/green rollout). Served so surfaces render the server's truth instead of keeping a copy that can drift: a field the server calls replica must be a field the UI calls replica. Any field not listed is replica.

## Response `200`

Spec field classification

- ServingSpecFieldList
  - `items` ServingSpecField[], required
    - `class` 'structural' | 'routing' | 'sizing' | 'replica', required — How a spec field may be changed. structural makes a different lane or tenant and is rejected everywhere. routing is safe to mutate under a running replica (PATCH). sizing is mutable by adding or removing replicas (/scale). replica requires new processes on new hardware, which is the blue/green trigger, and is the default for any field not listed.
    - `field` string, required

## Other responses

- `401` — Missing or invalid API key
- `403` — API key lacks the required scope
- `503` — A required integration (e.g. payments) is not configured

---

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