Verify user notification channel

Set the exact user/address stored verification flag after independent ownership proof; no challenge or delivery is performed.

Outcome

Set the exact user/address stored verification flag after independent ownership proof; no challenge or delivery is performed.

These examples prove local handler behavior with real isolated notification SQL and explicitly simulated identity dependencies.

Before you start

Verify pinned identity and the exact published action. Preference/address storage permits self or platform authority; organization admin alone cannot manage another user. Organization forbid rules require authority over the exact organization.
Discover the intended user/org independently. These storage handlers do not verify target existence and stored preference lists do not resolve effective delivery. Omitted preference org_id means global wildcard *, while replacement selects organization scope through query.org_id.
Before replacement capture the complete previous scope, review the full intended rows and inspect the validated plan. Empty rows clears explicit rules and may permit more delivery. Replacement is sequential and can leave partial state.
Channel verify only sets a stored flag and performs no possession challenge. Retain independent authorized ownership evidence before approving it; fixture addresses are unused and authorize no live verification or outreach.

Discover the target

topolo whoami --json
topolo apps --json
topolo actions get app_topolo_auth.user_notification_channels.verify --detail --json

Discover the authorized target user and exact organization. Read user_notification_preferences.list for each scope separately, user_notification_channels.list for stored channel_id values, or organization_notification_policy.list for the managed organization. Copy ids only from the exact selected scope. Effective delivery requires the published resolve action and delivery read-back separately.

Input fields

Field	Required	Meaning
`userId`	Yes	Existing intended Auth user from authorized discovery. User preference/address handlers allow self or platform authority; organization administrator alone does not authorize another user. These storage handlers do not independently verify target-user existence.
`channelId`	Yes	Stored channel_id read from the exact target user channels list or create response. Verify/delete bind both channelId and userId. It is not an email, device id or delivery receipt.

Effects

Sets the exact stored address verification timestamp if absent; repeating it keeps the prior timestamp.
No possession challenge or delivery is performed, and this flag may affect effective deliverability.

Interpret the response

Sets verified_at on the exact user/channel row if absent. Repeating it keeps the existing timestamp and returns the row.

This action performs no possession challenge or delivery verification. Do not treat its flag as proof of address ownership; use it only when the intended address has been independently verified through the authorized process. A concurrent missing post-update row can yield channel null, so read back.

Worked examples

These are complete raw target-handler responses, not CLI/gateway envelopes or live authorization proof. Synthetic users, organizations and unused addresses exist only in isolated fixtures. Discover real intended targets and review effects separately. Save only reviewed input as payload.json; validate and inspect the unchanged plan before an authorized call. --confirm assumes intended approval. Cookie/Bearer identities must consistently select the intended principal. Stored rows, ownership evidence, effective policy and actual delivered messages are separate outcomes. No fixture sends a message or performs an address challenge.

Mark the stored address verified without performing an ownership challenge

Input · payload.json:

{
  "userId": "usr_self",
  "channelId": "nch_DUthNOwIONWASRT_"
}

CLI:

topolo actions validate app_topolo_auth.user_notification_channels.verify --data @payload.json --json
topolo actions plan app_topolo_auth.user_notification_channels.verify --data @payload.json --confirm --json
topolo actions call app_topolo_auth.user_notification_channels.verify --data @payload.json --confirm --json

MCP call after validation and plan review:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_auth.user_notification_channels.verify",
    "input": {
      "userId": "usr_self",
      "channelId": "nch_DUthNOwIONWASRT_"
    },
    "confirm": true
  }
}

Captured local handler response · HTTP 200:

{
  "success": true,
  "message": "Notification channel verified",
  "data": {
    "userId": "usr_self",
    "channel": {
      "channel_id": "nch_DUthNOwIONWASRT_",
      "user_id": "usr_self",
      "channel": "email",
      "address": "fixture-address@example.test",
      "label": "Fixture email",
      "metadata_json": "{\"source\":\"isolated-doc-fixture\"}",
      "verified_at": 1790971419,
      "created_at": 1790971419
    }
  },
  "timestamp": "2026-10-02T00:00:00.000Z"
}

Repeat verify returns the already verified row and retains its timestamp

Input · payload.json:

{
  "userId": "usr_self",
  "channelId": "nch_DUthNOwIONWASRT_"
}

CLI:

topolo actions validate app_topolo_auth.user_notification_channels.verify --data @payload.json --json
topolo actions plan app_topolo_auth.user_notification_channels.verify --data @payload.json --confirm --json
topolo actions call app_topolo_auth.user_notification_channels.verify --data @payload.json --confirm --json

MCP call after validation and plan review:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_auth.user_notification_channels.verify",
    "input": {
      "userId": "usr_self",
      "channelId": "nch_DUthNOwIONWASRT_"
    },
    "confirm": true
  }
}

Captured local handler response · HTTP 200:

{
  "success": true,
  "message": "Notification channel verified",
  "data": {
    "userId": "usr_self",
    "channel": {
      "channel_id": "nch_DUthNOwIONWASRT_",
      "user_id": "usr_self",
      "channel": "email",
      "address": "fixture-address@example.test",
      "label": "Fixture email",
      "metadata_json": "{\"source\":\"isolated-doc-fixture\"}",
      "verified_at": 1790971419,
      "created_at": 1790971419
    }
  },
  "timestamp": "2026-10-02T00:00:00.000Z"
}

Verify the result

Require nonnull exact user/channel row with verified_at set and read the target channels list to confirm unrelated rows remain.
Retain independent authorized address-ownership evidence. Separately resolve intended events; no sent/delivered outcome follows from this flag.

Errors and recovery

Platform authority cannot mark another target user row through mismatched identifiers

Captured local refusal · HTTP 404:

{
  "input": {
    "userId": "usr_other",
    "channelId": "nch_DUthNOwIONWASRT_"
  },
  "response": {
    "success": false,
    "error": {
      "message": "Notification channel not found",
      "code": "NOT_FOUND",
      "details": null,
      "timestamp": "2026-10-02T00:00:00.000Z"
    }
  }
}

Anonymous address verification flag mutation is refused

Captured local refusal · HTTP 401:

{
  "input": {
    "userId": "usr_self",
    "channelId": "nch_DUthNOwIONWASRT_"
  },
  "response": {
    "success": false,
    "error": {
      "message": "Access token required",
      "code": "AUTH_ERROR",
      "details": null,
      "timestamp": "2026-10-02T00:00:00.000Z"
    }
  }
}

Published recovery guidance

state_conflict (HTTP 409): Read the current resource state, reconcile the intended change, and retry only if still valid.
AUTH_ERROR (HTTP 401): Verify pinned identity. If authenticated, respect self/platform user authority or exact organization management denial; organization ownership alone does not authorize another user address/preferences. Do not assume OAuth expiry or change context automatically.
VALIDATION_ERROR (HTTP 400): Correct the reported fields only. Use unique event/channel pairs and valid channel-specific addresses. Validate and review the exact complete replacement again before approval.
NOT_FOUND (HTTP 404): Refresh the target user channels list. A row for another user is not authorized by a known channel id; repeated delete is already absent, not a new successful deletion.
SERVER_ERROR (HTTP 500): Preserve the result and read the exact stored scope before any new write. A replacement may have deleted old rules and inserted only some new ones; review finishing the intended set or restoring the captured set as a new approved replacement.

Recovery boundaries

No unverify action is published in this family. Do not automatically delete a valid route. Read actual state and preserve authorization evidence; any separately approved delete/re-register changes the row id and loses verification history rather than undoing the original event.

Discovery and evidence

This record belongs to app_topolo_auth. Fixtures prove actual NotificationPreferencesController and AuthController authority, validation, canonical notification SQL, duplicate/address identity and sequential replacement failure boundaries. Authenticated identities and unused targets/addresses are simulated and second-insert SQL failures injected. No live storage, ownership challenge, notification, deployment or production publication is proved.