Archive subscription topic

Archive a subscription topic so it can no longer be used for new work. Its history is kept.

Outcome

Archive a subscription topic so it can no longer be used for new work. Its history is kept.

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:write; required workspace access is read_write. 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.
Obtain authorization for the documented effect or personal-data export before supplying CLI --confirm or MCP confirm:true.

Discover the target

topolo whoami --json
topolo actions get app_topolo_nurture.subscription_topics.archive --detail --json
topolo resources topolo-nurture --json
topolo workspaces list topolo-nurture --json
topolo actions get app_topolo_nurture.subscription_topics.list --detail --json

id: subscription topics record id in the selected workspace.

Request

POST /api/subscription-topics/{id}/archive

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	subscription topics record 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

Sets the subscription topic's status to archived; nothing is deleted.

Interpret the response

The returned identifier path is $.topic.id for topic. Empty lists do not discover a target.

Call app_topolo_nurture.subscription_topics.get and confirm status is archived.

Exact success schema:

{
  "type": "object",
  "required": [
    "topic"
  ],
  "properties": {
    "topic": {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        },
        "key": {
          "type": "string"
        },
        "name": {
          "type": "string"
        },
        "description": {
          "type": [
            "string",
            "null"
          ]
        },
        "doubleOptIn": {
          "type": "boolean"
        },
        "status": {
          "type": "string"
        },
        "createdAt": {
          "type": "string"
        },
        "updatedAt": {
          "type": "string"
        }
      }
    }
  }
}

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": "topic_1f7781fc4540498795ce98b9a5b186c0"
}

CLI:

topolo actions validate app_topolo_nurture.subscription_topics.archive --data @payload.json --json
topolo actions plan app_topolo_nurture.subscription_topics.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.subscription_topics.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_nurture.subscription_topics.archive",
    "input": {
      "id": "topic_1f7781fc4540498795ce98b9a5b186c0"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "topic": {
    "id": "topic_1f7781fc4540498795ce98b9a5b186c0",
    "key": "news",
    "name": "News",
    "description": null,
    "doubleOptIn": true,
    "status": "archived",
    "createdAt": "2026-10-04T00:32:34.803Z",
    "updatedAt": "2026-10-04T00:32:34.811Z"
  }
}

HTTP 200. Call app_topolo_nurture.subscription_topics.get and confirm status is archived.

Another supported request

Input · payload.json:

{
  "id": "topic_f15a2b4423ae496e8753e994e548d80a"
}

CLI:

topolo actions validate app_topolo_nurture.subscription_topics.archive --data @payload.json --json
topolo actions plan app_topolo_nurture.subscription_topics.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.subscription_topics.archive --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_nurture.subscription_topics.archive",
    "input": {
      "id": "topic_f15a2b4423ae496e8753e994e548d80a"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "topic": {
    "id": "topic_f15a2b4423ae496e8753e994e548d80a",
    "key": "news",
    "name": "News",
    "description": null,
    "doubleOptIn": true,
    "status": "archived",
    "createdAt": "2026-10-04T00:32:37.586Z",
    "updatedAt": "2026-10-04T00:32:37.601Z"
  }
}

HTTP 200. Call app_topolo_nurture.subscription_topics.get and confirm status is archived.

Refused request · not_found

Input · payload.json:

{
  "id": "topic_431d90997c244ab594c9f5f19f56fd7d"
}

CLI:

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

Captured local response · HTTP 404:

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

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

Verify the result

Call app_topolo_nurture.subscription_topics.get and confirm status is archived.

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 subscription topics 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

Archiving cannot be undone; create a new subscription topic if it is needed again.

List subscription topics: List the subscription topics in the caller's Nurture workspace, optionally filtered by status. Topics are what a contact can subscribe to in the preference centre; the contact's choice itself is held by TopoloConsent.

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.

Archive subscription topic

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