---
title: "Retrieve Task Run Input"
method: GET
path: "/v1/tasks/runs/{run_id}/input"
tags: ["Tasks v1"]
---

# Retrieve Task Run Input

`GET /v1/tasks/runs/{run_id}/input`

Retrieves the input of a run by run_id.

## Path parameters

- `run_id` string, required

## Response `200`

Successful Response

- TaskRunInput — Request to run a task.
  - `input` union, required — Input to the task, either text or a JSON object.
    - string
    - object
  - `metadata` object, nullable — User-provided metadata stored with the run. Keys and values must be strings with a maximum length of 16 and 512 characters respectively.
  - `processor` string, required — Processor to use for the task.
  - `source_policy` SourcePolicy — Source policy for web search results. This policy governs which sources are allowed/disallowed in results.
    - `after_date` string, date, nullable — Optional start date for filtering search results. Results will be limited to content published on or after this date. Provided as an RFC 3339 date string (YYYY-MM-DD).
    - `exclude_domains` string[] — List of domains to exclude from results. If specified, sources from these domains will be excluded. Accepts plain domains (e.g., example.com, subdomain.example.gov) or bare domain extension starting with a period (e.g., .gov, .edu, .co.uk).
    - `include_domains` string[] — List of domains to restrict the results to. If specified, only sources from these domains will be included. Accepts plain domains (e.g., example.com, subdomain.example.gov) or bare domain extension starting with a period (e.g., .gov, .edu, .co.uk).
  - `task_spec` TaskSpec — Specification for a task. Auto output schemas can be specified by setting `output_schema={"type":"auto"}`. Not specifying a TaskSpec is the same as setting an auto output schema. For convenience bare strings are also accepted as input or output schemas.
    - `input_schema` union — Optional JSON schema or text description of expected input to the task. A bare string is equivalent to a text schema with the same description.
      - string
      - JsonSchema — JSON schema for a task input or output.
        - `json_schema` object, required — A JSON Schema object. Only a subset of JSON Schema is supported.
        - `type` 'json' — The type of schema being defined. Always `json`.
      - TextSchema — Text description for a task input or output.
        - `description` string, nullable — A text description of the desired output from the task.
        - `type` 'text' — The type of schema being defined. Always `text`.
    - `output_schema` union, required — JSON schema or text fully describing the desired output from the task. Descriptions of output fields will determine the form and content of the response. A bare string is equivalent to a text schema with the same description.
      - JsonSchema — JSON schema for a task input or output.
        - `json_schema` object, required — A JSON Schema object. Only a subset of JSON Schema is supported.
        - `type` 'json' — The type of schema being defined. Always `json`.
      - TextSchema — Text description for a task input or output.
        - `description` string, nullable — A text description of the desired output from the task.
        - `type` 'text' — The type of schema being defined. Always `text`.
      - AutoSchema — Auto schema for a task input or output.
        - `type` 'auto' — The type of schema being defined. Always `auto`.
      - string

## Other responses

- `401` — Unauthorized: invalid or missing credentials
- `404` — Run id not found
- `422` — Request validation error

## Changes

- **2026-01-13** `105d778ad64d` — 3 breaking, 21 info
  - the `error` response's property type/format changed from ``/`` to `object`/`` for status `401`
  - the `error` response's property type/format changed from ``/`` to `object`/`` for status `404`
  - the `error` response's property type/format changed from ``/`` to `object`/`` for status `422`
  - added the optional property `error/detail` to the response with the `401` status
  - …20 more
- **2025-11-06** `a2d634b57a8e` — 2 info
  - api tag `Tasks v1` added
  - api tag `Task API v1` removed
- **2025-09-15** `ed59cb6466c0` — 4 breaking
  - the response property `task_spec/anyOf[subschema #1: TaskSpec]/input_schema/anyOf[subschema #3: TextSchema]/description` became optional for the status `200`
  - the response property `task_spec/anyOf[subschema #1: TaskSpec]/output_schema/anyOf[subschema #2: TextSchema]/description` became optional for the status `200`
  - response property `task_spec/anyOf[subschema #1: TaskSpec]/input_schema/anyOf[subschema #3: TextSchema]/description` list-of-types was widened by adding types `null` to media type `application/json` of response `200`
  - response property `task_spec/anyOf[subschema #1: TaskSpec]/output_schema/anyOf[subschema #2: TextSchema]/description` list-of-types was widened by adding types `null` to media type `application/json` of response `200`
- …earlier changes not shown

[Full history](https://skmtc.dev/parallel-web/apis/parallel-api/changes/v1/tasks/runs/:run_id/input/get.md)

---

[API](https://skmtc.dev/parallel-web/apis/parallel-api.md) · [All operations](https://skmtc.dev/parallel-web/apis/parallel-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/parallel-web/parallel-api/revisions/31ff2f5e2e00/schema)