> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# POST /v1/monitors/{monitor_id}/delivery

> Update or replace the monitor's delivery destination (e.g., set or change an email recipient)

Update or replace the monitor's delivery destination (e.g., set or change an email recipient)

<Info>
  Audience: signed-in organization administrator.
</Info>

## Replacing a destination

Send one supported delivery destination. An email destination can require activation; Situation webhook watches require organization-level event fanout and an active webhook endpoint or stream target before the monitor can be updated. A successful configuration response is not a delivery receipt.

## Canonical metadata

* `requestId`
* `traceparent`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X POST \
    -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
    -H "secapi-version: 2026-03-19" \
    -H "content-type: application/json" \
    -d '{"type":"email","config":{"to":"alerts@example.com"}}' \
    "https://api.secapi.ai/v1/monitors/mon_example_123/delivery"
  ```
</RequestExample>

<Info>
  This organization control-plane action requires a signed-in WorkOS browser session. Do not give an API key or an autonomous agent authority to create, change, test, replay, rotate, or delete it.
</Info>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Explain the required fields for POST /v1/monitors/{monitor_id}/delivery, but direct the user to complete the change in the signed-in SEC API dashboard. Do not attempt the mutation with an API key or an autonomous agent. Preserve requestId and traceparent when the dashboard or a human-authenticated session returns them.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff