List contact subscriptions

Read a contact's subscription state for every active topic of the workspace: none, pending_confirmation, subscribed or unsubscribed, with since and the evidence that subscribed them. State is resolved by @topolo-io/audience from Nurture's own subscription stream and suppression ledger; an unsubscribe is always a ledger event.

Outcome

Before you start

Verify identity and pin the intended organization and environment before discovering the action.
Discover a granted Nurture workspace. The application permission is workspace:read; required workspace access is read. A permission alone does not supply a workspace grant.
Organization and workspace come from verified context. Select resourceType/resourceId separately from action input; body fields cannot grant a different organization or workspace. The first authorized product action can initialize an identity-only workspace mirror.

Discover the target

topolo whoami --json
topolo actions get app_topolo_nurture.subscriptions.list --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
topolo actions get app_topolo_nurture.contacts.list --detail --json

id: Nurture contact id in the selected workspace.

Request

GET /api/contacts/{id}/subscriptions

Save action input as payload.json. The reviewed plan separates path identifiers, query fields and HTTP body. Set NURTURE_WORKSPACE_ID from granted resource discovery; it is separate from action input.

Inspect and test this action in the signed action console. A test response still requires the verification below.

Input fields

Field	Required	Type	Constraints
`id`	Required	string	Nurture contact id in the selected workspace. {"minLength":1,"maxLength":64}

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Effects

Reads subscription state without changing it.

Interpret the response

The returned identifier path is $.contactId for contact. Empty lists do not discover a target.

Confirm $.contactId equals the requested contact and one entry exists per active topic.

Exact success schema:

{
  "type": "object",
  "required": [
    "contactId",
    "subscriptions"
  ],
  "properties": {
    "contactId": {
      "type": "string"
    },
    "subscriptions": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "topicKey",
          "state"
        ],
        "properties": {
          "topicKey": {
            "type": "string"
          },
          "topicId": {
            "type": "string"
          },
          "topicName": {
            "type": "string"
          },
          "doubleOptIn": {
            "type": "boolean"
          },
          "state": {
            "type": "string",
            "enum": [
              "none",
              "pending_confirmation",
              "subscribed",
              "unsubscribed"
            ]
          },
          "since": {
            "type": [
              "string",
              "null"
            ]
          },
          "evidence": {
            "type": [
              "array",
              "null"
            ],
            "items": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Worked examples

Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Replace synthetic identifiers using credential-scoped discovery. A local success is not evidence of a deployed effect, configured provider or delivered message.

Successful request

Actual dispatcher and migration-created SQLite; verified identity/workspace and external CRM, Engage, Notify, Consent, Nexus, Brand, Generator, Voice and delivery dependencies are simulated. No live authorization, paid generation or external delivery is established.

Input · payload.json:

{
  "id": "nct_5343bec9ee3743269b15515100f009ff"
}

CLI:

topolo actions validate app_topolo_nurture.subscriptions.list --data @payload.json --json
topolo actions plan app_topolo_nurture.subscriptions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.subscriptions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_nurture.subscriptions.list",
    "input": {
      "id": "nct_5343bec9ee3743269b15515100f009ff"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "contactId": "nct_5343bec9ee3743269b15515100f009ff",
  "subscriptions": [
    {
      "topicKey": "digest",
      "topicId": "topic_6479c2fe755a47d9883a3e6ff6124dd6",
      "topicName": "Digest",
      "doubleOptIn": false,
      "state": "none",
      "since": null,
      "evidence": null
    },
    {
      "topicKey": "news",
      "topicId": "topic_921562fd62f9455d8413b97c201b3367",
      "topicName": "News",
      "doubleOptIn": true,
      "state": "unsubscribed",
      "since": "2026-10-01T00:24:00.002Z",
      "evidence": null
    }
  ]
}

HTTP 200. Confirm $.contactId equals the requested contact and one entry exists per active topic.

Another supported request

Input · payload.json:

{
  "id": "nct_f4095688094d4d2dbdfe8c7286d89d25"
}

CLI:

topolo actions validate app_topolo_nurture.subscriptions.list --data @payload.json --json
topolo actions plan app_topolo_nurture.subscriptions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.subscriptions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_nurture.subscriptions.list",
    "input": {
      "id": "nct_f4095688094d4d2dbdfe8c7286d89d25"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "contactId": "nct_f4095688094d4d2dbdfe8c7286d89d25",
  "subscriptions": [
    {
      "topicKey": "digest",
      "topicId": "topic_ea4a532b908a42babae3316420979d27",
      "topicName": "Digest",
      "doubleOptIn": false,
      "state": "none",
      "since": null,
      "evidence": null
    },
    {
      "topicKey": "news",
      "topicId": "topic_7feb1bf0f64f4a0497785ee3dcb4fbea",
      "topicName": "News",
      "doubleOptIn": true,
      "state": "subscribed",
      "since": "2026-10-01T00:24:00.002Z",
      "evidence": [
        {
          "kind": "double_opt_in",
          "tokenHash": "6379586bcee2cf8cf23d7180e832a6b91f83c0e2d130db4c5689a73a8930e080",
          "requestedAt": "2026-10-01T00:24:00.001Z",
          "confirmedAt": "2026-10-01T00:24:00.002Z"
        }
      ]
    }
  ]
}

HTTP 200. Confirm $.contactId equals the requested contact and one entry exists per active topic.

Refused request · not_found

Input · payload.json:

{
  "id": "nct_4945f75a6f054baa89c0d210c36204ed"
}

CLI:

topolo actions validate app_topolo_nurture.subscriptions.list --data @payload.json --json
topolo actions plan app_topolo_nurture.subscriptions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 404:

{
  "error": {
    "code": "not_found",
    "message": "Contact was not found in this workspace."
  }
}

HTTP 404. Preserve the refusal details and do not claim success.

Verify the result

Confirm $.contactId equals the requested contact and one entry exists per active topic.

Errors and recovery

organization_required (HTTP 403): Select an organization available to the verified caller before choosing a Nurture workspace.
permission_denied (HTTP 403): Grant the credential the required Nurture workspace permission.
workspace_required (HTTP 409): Create a Nurture workspace, or pass the workspace resource context.
invalid_input (HTTP 422): Correct the fields named in error.details using inputSchema, then retry.
not_found (HTTP 404): List contacts to find a valid id in this workspace.

Auth or gateway failures may precede this handler. Preserve the exact response shape, error string/code, request id and credential context; no synthetic fixture establishes live credential access.

Recovery boundary

This action does not change service state.

Subscribe contact with evidence: Subscribe a contact to an active topic on the strength of evidence. consent_decision (provider, decisionRef, purposeId) always subscribes, also after an unsubscribe. import_attestation (importId, lawfulBasis; attestedBy is the caller) is accepted only as the contact's very first subscription to the topic, never after an unsubscribe, and never for a topic with doubleOptIn true. For double opt-in use subscriptions.request_confirmation instead; double_opt_in evidence is only ever produced by the public confirmation link. Marketing delivered through Nexus is attested to Nexus from the latest double opt-in, repermission or consent_decision record; an import_attestation alone is not consent and the send skips with no_consent_evidence.
Request double opt-in confirmation: Start double opt-in for a contact and an active topic: records subscribe_requested (state pending_confirmation) and returns confirmationUrl, a signed single-use link valid for 7 days (only its hash is stored). Opening the link (GET) only shows a page with a Confirm subscription button and never changes state, so email link scanners cannot confirm; the button POSTs the token, which confirms the subscription with double_opt_in evidence. With a verified sender (sending_settings) Nurture emails the link through Nexus (transactional, service_notice) and reports it in email; without one email.status is not_configured: deliver confirmationUrl yourself. Never confirm on the contact's behalf.
Unsubscribe contact from topic: Unsubscribe a contact from one topic (active or archived) by appending a topic-scoped unsubscribed event to the suppression ledger, the single source of unsubscribes. Marketing for that topic is blocked until the contact re-subscribes with double opt-in or a consent decision.

Evidence

Actual dispatcher and migration-created SQLite or Worker handlers; identity/workspace and external service dependencies are simulated. Fixture identifiers and timestamps are synthetic. These responses establish no live authorization, paid generation, credential provisioning or message delivery. Test scenario and capture digests are retained with each fixture.

List contact subscriptions

Outcome

Before you start

Discover the target

Request

Input fields

Effects

Interpret the response

Worked examples

Successful request

Another supported request

Refused request · not_found

Verify the result

Errors and recovery

Recovery boundary

Related actions

Evidence