---
title: "Pause or resume an agent"
method: PUT
path: "/v1/agents/{id}/state"
tags: ["Agents"]
---

# Pause or resume an agent

`PUT /v1/agents/{id}/state`

## Request

- Base URL: `https://docs.grepr.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://docs.grepr.ai/v1/agents/{id}/state`
- Auth: one of:
  - API key in header `GREPR-API-KEY`
  - OpenID Connect (`https://grepr-prod.us.auth0.com/.well-known/openid-configuration`)

Sets the agent to PAUSED or ACTIVE. A paused agent runs no investigations: signals from every source are dropped, manual starts and resumes are refused, and queued investigations wait until the agent is resumed, except those on an issue, which are discarded so other agents can take the issue. Pipelines keep marking new patterns as sent, so after resuming, the agent usually reacts only to patterns that are new since then.

## Path parameters

- `id` string, required

## Request body

- StateChangeRequest
  - `state` 'ACTIVE' | 'PAUSED', required

## Response `204`

State set (or already set)

## Other responses

- `400`: The state is not ACTIVE or PAUSED
- `401`: Unauthorized
- `404`: Agent not found

---

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