Retrieve a schema

Returns the detail resource for one schema: its name, its requestType, and resultsFields — every field the schema can produce in results on GET /v1/requests/{requestId}. Use it to build an ingest mapping and a destination table before you run a request. Inputs are not included; use GET /v1/schemas/{schemaId}/required-inputs for what to send.

resultsFields is sorted by name. Each name matches the results key and the top-level missingFields entries exactly. callSteps[].missingFields is a different list — it falls back to raw question text for a skipped question that carries no alias — so do not join it against this inventory.

For this schema, the inventory is a superset of any one response. Most fields on a large schema are gated on another field's answer, so they are absent on any given request. An unanswered field is absent from results; it is never null. Every column you build from this inventory must be nullable. Map on name, treat every field as optional, and ignore keys you do not map. The endpoint does not report which fields are gated.

A chained request can return keys beyond this schema. A request can open a follow-up leg: a second call against a different schema, visible as an extra callSteps entry. That leg's captured values merge into the same top-level results under the leg schema's own field names. resultsFields covers one schema and does not list them. Read callSteps[].schemaId on a completed request, then call this endpoint again for that id.

allowedValues is not a closed set. CANNOT ANSWER - <reason> passes through verbatim as a string on any type, including boolean and multiple, so a strict enum or boolean parse fails on it. Detect it by string prefix. It does not appear in missingFields: an explicit non-answer counts as answered.

Version drift. resultsFields describes the schema's current latest version. A request that already ran was pinned to the version that was latest at run time. So an older request's results can carry keys this endpoint no longer lists, or omit keys it now lists. Read the endpoint again and diff the field list to find a change.