User Channel Addresses
Link notification channel addresses through API v1.
All endpoints require authentication and an active user. A user may manage their own addresses; notifications.manage permits administrators to manage another user. Read operations require users:read; changes require users:write.
Endpoints
| Method | URL | Summary | Ability | Weight |
|---|---|---|---|---|
GET | /api/v1/users/{user}/channel-addresses | Channel Addresses users | users:read | 1 |
PUT | /api/v1/users/{user}/channel-addresses/{channel} | Channel Addresses users | users:write | 1 |
POST | /api/v1/users/{user}/channel-addresses/{channel}/confirm | Channel Addresses users | users:write | 1 |
POST | /api/v1/users/{user}/channel-addresses/{channel}/verification | Channel Addresses users | users:write | 1 |
The channel must have a registered address descriptor. Driver normalization and validation apply. Responses expose channel, channel_provider_id, address and verification time, never encrypted connection metadata or verification hashes. Admin updates for another user are verified. Bulk linking repeats the PUT endpoint under the same authorization and idempotent user/channel key. Codes expire in ten minutes and allow five attempts; sending is throttled.
Channel-provider responses additionally expose warehouse_id, only_verified_addresses, latest delivery status/message ID, driver address descriptors and rich config schemas. Secret config remains masked. Test recipients are free-form driver-validated strings. MCP list-channel-providers uses the same API representation.
Workflow definition validation returns warnings keyed by JSON pointer for unavailable channel overrides. Dynamic channel options are supplied by each handler's schema, including the optional restriction on notifications.send. validate-workflow-definition exposes the same warnings through MCP.
All three mutation payloads accept optional channel_provider_id. Omit it or use null to edit the generic address. A supplied ID must be an active provider of that channel. Each provider can have a separate address and verification code; confirming one does not verify another. For example, use {"address":"user-123","channel_provider_id":23} to save, {"channel_provider_id":23} to send its code, and {"code":"123456","channel_provider_id":23} to confirm it. Delivery chooses the provider-specific row before the generic fallback. OAuth connections are stored against the connected provider, and settings offers separate Connect controls for multiple providers.