Skip to main content
POST
Selects one random person with matching live diffs from the recent Monitoring result set and sends a digest to the configured destinations. The digest can contain multiple matching changes for that person. This endpoint performs real delivery side effects; it is not a dry run. It looks back up to 30 days and considers up to 80 Monitoring rows, then chooses one matching row. Demo diffs are excluded.

Request body

The body is optional. Send {} or omit the body.
string[]
Optional extra email recipients for this send. String entries containing @ are accepted, trimmed, lowercased, and deduplicated with organization member and saved preference addresses. No endpoint-specific maximum is defined in the Gateway route. Invalid array items are ignored.
The saved notification preferences still control whether email or Slack is attempted. An extra email does not force email on when email_enabled is false.

Response

200
person, email, and slack are strings. email can be sent, disabled, skipped-no-recipients, or skipped-no-api-key. slack can be sent, disabled, not_connected, or skipped-no-channel. A 200 with skipped-* does not mean a message was delivered. sent means the downstream send call accepted the message; it is not a provider delivery guarantee.

Actual delivery and retry safety

  • If email is enabled, the Gateway resolves organization member addresses plus saved preference addresses and any emails in this request, then calls the configured email provider. No recipients produces skipped-no-recipients; a missing email-provider API key produces skipped-no-api-key.
  • If Slack is enabled, the Gateway posts to the installed workspace’s selected channel. No installation produces not_connected; an installation without a selected channel produces skipped-no-channel.
  • Repeating this POST can send another email or Slack message. There is no idempotency key and no test-specific rate limit in the Gateway route. Do not automatically retry after a timeout or uncertain 5xx; first check the destinations and provider logs, because the first send may already have happened.
  • The shared Gateway limit is 300 requests per minute per client IP. Honor Retry-After on 429; this limit does not prevent the downstream provider or Slack from applying its own limits.

Errors