Deploy Webhook

A deploy webhook fires a project's tests after a successful deploy — asynchronously, in the background. Results land in the dashboard; the pipeline does not wait for them. If the pipeline should block on results, use the CI integration instead.

Get the URL and secret

Open your project in the dashboard, select Automations, then Deploy webhook. The panel shows the project's webhook URL. Rotating the secret displays it exactly once — store it in your deploy environment as MONITO_WEBHOOK_SECRET.

Fire the webhook

After a successful deploy, POST to the webhook URL with the secret as a bearer token:

curl -X POST "$MONITO_WEBHOOK_URL" \
  -H "Authorization: Bearer $MONITO_WEBHOOK_SECRET"

A successful call returns 202 with the queued run IDs and a results URL. It means the tests are queued — not that they passed.

An optional JSON body narrows or overrides what runs:

Field	Description
`env`	Environment name to run against (default: the project's default environment)
`suite`	Suite name to run (default: all tests)
`scenarioIds`	Explicit list of scenario IDs to run
`baseUrlOverride`	Test a transient origin instead, e.g. a preview deploy URL

curl -X POST "$MONITO_WEBHOOK_URL" \
  -H "Authorization: Bearer $MONITO_WEBHOOK_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"env": "Staging", "suite": "Smoke"}'

With an AI agent

An agent can wire the webhook into your deploy pipeline for you. From the dashboard's deploy webhook panel, copy the agent prompt — it carries the webhook URL and instructs the agent to read the secret from your deploy environment, never to hardcode it.

Rotate or disable

Rotating invalidates the old secret immediately; update MONITO_WEBHOOK_SECRET in your deploy environment. Disabling (or deleting the webhook automation with monito automation delete) turns the integration off — subsequent calls return 401. See automation.

Get the URL and secret

Fire the webhook

With an AI agent

Rotate or disable

On this page