Agent

Trigger a real test notification

Synthesizes a sample organization_past_due event and pushes it through the normal worker pipeline (email/webhook), AND — independently — delivers a synthetic event through the caller's Telegram routing rules (notification-channel-routing-telegram, v1.126), so one call verifies the full binding+rule+render+send chain end-to-end. Audit rows are marked is_test=true. Rate-limited per wallet at 1/min.

post/agent/v1/notifications/test

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/agent/v1/notifications/test
  • Auth: API key in header SIGN-IN-WITH-X

Headers

SIGN-IN-WITH-Xstring required

SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.

Request body

source'app' | 'platform'
event_typestring

Flat snake_case, ^[a-z][a-z0-9_]{2,63}$.

severity'info' | 'notice' | 'warn' | 'critical'

event-attention-rules: the synthetic event's severity, so a rule at the default minimum matches it. A rule whose minimum sits above it is reported under telegram.skipped_rules instead of staying silently unmatched. Any other value is 400 INVALID_SEVERITY.

Response

Queued

status'queued'
source_event_idstring
notestring

Changes

No recorded changes to this operation across all 1 revision of this API.