Topolo Docs Topolo Platform
Open workspace

List Mail mailboxes

List accessible mailbox profiles in the selected canonical workspace.

Outcome

List accessible mailbox profiles in the selected canonical workspace.

Before you start

  • Verify the intended environment, credential and authorized organization context before discovery.
  • Discover Mail, the exact action and its mailboxes:read permission. Pass the accessible workspace resource binding separately from action input.

Discover the target

  • Run credential-scoped Mail discovery and topolo workspaces list topolo-mail; select an authorized canonical workspace.
  • Resolve mailbox IDs through mailboxes.collection.list in that workspace. Resolve message, draft, thread, folder and scheduled IDs through the related published reads; never reuse fixture IDs or another context.
topolo whoami --json
topolo apps get topolo-mail --json
topolo actions get app_topolo_mail.mailboxes.collection.list --json
topolo workspaces list topolo-mail --json

Request

Create payload.json using the current input schema and discovered identifiers. Plan the unchanged request before execution.

topolo actions validate app_topolo_mail.mailboxes.collection.list --data @payload.json --json
topolo actions plan app_topolo_mail.mailboxes.collection.list --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --json
topolo actions call app_topolo_mail.mailboxes.collection.list --resource-type workspace --resource-id <discovered-workspace-id> --data @payload.json --json

For MCP, use topolo_get_action, topolo_validate_action and topolo_plan_action; execute with topolo_read_action. Pass resourceType workspace and the discovered resourceId separately from input. An absent service/action or non-executable plan blocks that operation.

Input fields

This action accepts an empty input object. Keep workspace context separate.

Effects

  • Reads caller-visible mailbox profiles and their connection metadata.

Interpret the response

data is an array, not data.mailboxes. Each id is a mailbox ID distinct from workspaceId. Profiles include connectionType and connectionStatus but do not prove provider delivery.

Worked requests and responses

Successful fixture request · HTTP 200

Input

{}

SDK response or error

{
  "success": true,
  "data": [
    {
      "id": "mbx_mail_fixture",
      "organizationId": "org_mail_fixture",
      "workspaceId": "ws_mail_fixture",
      "userId": "usr_mail_fixture",
      "organizationSlug": null,
      "address": "fixture@example.test",
      "displayName": "Fixture mailbox",
      "fromName": "Fixture sender",
      "replyToAddress": "fixture@example.test",
      "status": "active",
      "agentPrompt": "Fixture assistant",
      "outboundProfileId": null,
      "connectionType": "topolo_hosted",
      "connectionStatus": "active",
      "connectionStatusReason": null,
      "providerIdentity": null,
      "lastSyncAt": null,
      "createdAt": "2026-10-08T00:00:00.000Z",
      "updatedAt": "2026-10-08T00:00:00.000Z"
    }
  ]
}

Refused requests

Unauthenticated caller · HTTP 401

Input

{}

SDK response or error

{
  "code": "auth_error",
  "status": 401,
  "message": "Fixture authentication refused"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "Fixture authentication refused"
  }
}

Permission denied · HTTP 403

Input

{}

SDK response or error

{
  "code": "permission_denied",
  "status": 403,
  "message": "TopoloMail permission denied"
}

Service HTTP body

{
  "success": false,
  "error": {
    "message": "TopoloMail permission denied"
  }
}

Verify the result

  • Verify each returned organizationId/workspaceId before using its id in a mailbox action. An empty result is not permission to guess an ID.

Recover

This read requests no delivery or data change. Preserve failures and repeat discovery in the same authorized context; no rollback mutation is needed.

  • HTTP 401 auth_error: Authenticate again in the intended environment and context, then repeat identity and action discovery.
  • HTTP 403 permission_denied: Stop for the exact permission, organization, sender or Reply-To refusal. Do not broaden access or switch credentials automatically.

The captured SDK errors preserve the service code when structured, otherwise http_error and HTTP status. Do not invent a more specific code. Preserve the live request ID and inspect actual diagnostics for uncaptured failures.

Evidence and limits

  • Actual exported Mail handler dispatcher, widget handler, domain handlers, SDK transport/projection and shipped SQLite control/delivery/tracking migrations.

  • Identity, permissions, verified workspace grants, provider connection state, OAuth URL generation, mailbox Durable Object operations and content protection are synthetic ports.

  • Nexus AI and Auth archive are allowlisted in-process responses. No paid generation, billing, live OAuth, encryption custody, email delivery, asynchronous delivery or deployed outcome is proved. External network egress is refused.

The captured requests use synthetic identities and .test recipients. They demonstrate handler and SDK response behavior; they do not authorize delivery, provider consent, paid generation, deletion or other live effects. Current catalog discovery and environment proof remain separate release requirements.