---
title: "Trigger Job"
method: GET
path: "/job/{runchat_job_id}"
tags: ["Jobs"]
---

# Trigger Job

`GET /job/{runchat_job_id}`

## Request

- Base URL: `https://runchat.com/api/v1`
- URL: `https://runchat.com/api/v1/job/{runchat_job_id}`
- Auth: HTTP bearer

Triggers a saved Runchat job. If the job is backed by a flow it runs the flow's scheduled inputs. If the job is backed by an agent chat it replays the saved messages and runs the agent loop unattended.

A new row is written to `runchat_job_history` for every invocation, with the resulting flow state (and, for agent jobs, the message transcript) persisted to R2.

## Response `200`

Successful job execution.

- union
  - FlowJobResponse: Response shape for flow-backed job runs (GET only).
    - `metadata` string, json: Stringified JSON containing execution metadata.
    - `data` BasicParameter[]: Output data from the executed nodes.
      - `id` string, required: Unique identifier for the parameter, often in the format 'paramKey_parentNodeId'.
      - `label` string, required: User-friendly label for the parameter.
      - `type` 'string' | 'number' | 'boolean' | 'object' | 'image' | 'video' | 'audio' | 'model' | 'message' | 'context' | 'code' | 'array' | 'instruction' | 'null' | 'markdown' | 'file' | 'format' | 'html' | 'pdf' | 'trigger' | 'select', required: Enumeration of supported data types within Runchat.
      - `description` string, required: Description of the parameter.
      - `data` object[], required: The actual data associated with the parameter, represented as an array of items.
    - `job_id` string: The job identifier.
    - `runchat_id` string: The underlying Runchat identifier.
  - AgentJobResponse: Response shape for agent-backed job runs.
    - `metadata` string, json: Stringified JSON containing the agent run metadata (token counts, credits, etc.).
    - `messages` object[]: Final transcript including the saved template, any appended user message, and the agent's responses.
    - `job_id` string: The job identifier.
    - `runchat_id` string: The underlying Runchat identifier.
    - `status` 'success' | 'error': Outcome of the agent run.
    - `error` string: Error message, present only when `status` is `error`.

## Other responses

- `400`: Bad Request - The request could not be understood or was missing required parameters.
- `403`: Access denied — user does not have permission to the underlying Runchat.
- `404`: Job or Runchat not found.
- `500`: Internal Server Error - An unexpected error occurred on the server.

---

[API](https://skmtc.dev/runchat/apis/runchat-api.md) - [All operations](https://skmtc.dev/runchat/apis/runchat-api/llms.txt) - [OpenAPI document](https://skmtc.dev/runchat/apis/runchat-api/revisions/4fa3fd81ab51?raw)