---
title: "Trigger a Monitor"
method: POST
path: "/monitors/{id}/trigger"
tags: ["Monitors"]
---

# Trigger a Monitor

`POST /monitors/{id}/trigger`

Triggers a run immediately, regardless of the schedule. Works for monitors with status `active` or `paused`.

## Path parameters

- `id` string, required — The monitor ID

## Response `200`

Whether the monitor was triggered

- TriggerSearchMonitorResponse
  - `triggered` boolean, required — Whether the monitor was successfully triggered

## Other responses

- `400` — The request body or query parameters failed validation.
- `401` — The API key is missing or invalid.
- `404` — The requested resource does not exist.
- `500` — An unexpected error occurred while processing the request.

## Changes

- **2026-08-27** `67abccbd77b6` — 1 warning
  - deleted the `header` request parameter `Exa-Version`
- **2026-08-26** `bcc51991b48a` — 1 info
  - added the new optional `header` request parameter `Exa-Version`
- **2026-08-25** `659cf16a7325` — 4 info
  - added the non-success response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `404`
  - added the non-success response with the status `500`

[Change history](https://skmtc.dev/exa/apis/exa-public-api/changes/monitors/:id/trigger/post.md)

---

[API](https://skmtc.dev/exa/apis/exa-public-api.md) · [All operations](https://skmtc.dev/exa/apis/exa-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/exa/exa-public-api/revisions/67abccbd77b6/schema)