Topolo Docs Topolo Platform
Open workspace

List contact suppressions

Read the suppression blocks currently active for a contact (resolved by @topolo-io/audience, stricter wins) and the ledger events behind them. Address-scoped events (hard_bounce, deliverable, complaint, wrong_person, and erased, which contacts.erase records and nothing lifts) are keyed by the org-scoped address hash and apply across every workspace of the organization, so events may come from other workspaces; events are therefore shown without contact ids, address hashes or evidence details.

Outcome

Read the suppression blocks currently active for a contact (resolved by @topolo-io/audience, stricter wins) and the ledger events behind them. Address-scoped events (hard_bounce, deliverable, complaint, wrong_person, and erased, which contacts.erase records and nothing lifts) are keyed by the org-scoped address hash and apply across every workspace of the organization, so events may come from other workspaces; events are therefore shown without contact ids, address hashes or evidence details.

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.suppressions.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}/suppressions

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

FieldRequiredTypeConstraints
idRequiredstringNurture 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 ledger 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; blocks[] empty means nothing suppresses the contact.

Exact success schema:

{
  "type": "object",
  "required": [
    "contactId",
    "blocks",
    "events"
  ],
  "properties": {
    "contactId": {
      "type": "string"
    },
    "blocks": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "code",
          "purpose",
          "scope",
          "since"
        ],
        "properties": {
          "code": {
            "type": "string"
          },
          "purpose": {
            "type": "string",
            "enum": [
              "marketing",
              "outreach",
              "all"
            ]
          },
          "scope": {
            "type": "string",
            "enum": [
              "contact",
              "address"
            ]
          },
          "topicKey": {
            "type": "string"
          },
          "since": {
            "type": "string"
          },
          "sourceApp": {
            "type": "string"
          }
        }
      }
    },
    "events": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "idempotencyKey",
          "type",
          "scope",
          "occurredAt"
        ],
        "properties": {
          "idempotencyKey": {
            "type": "string"
          },
          "type": {
            "type": "string"
          },
          "scope": {
            "type": "string",
            "enum": [
              "contact",
              "address"
            ]
          },
          "topicKey": {
            "type": "string"
          },
          "occurredAt": {
            "type": "string"
          },
          "sourceApp": {
            "type": "string"
          },
          "reason": {
            "type": [
              "string",
              "null"
            ]
          },
          "evidenceKinds": {
            "type": "array",
            "items": {
              "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": "nct_e5477c912eff49b8949f71490c2ded25"
}

CLI:

topolo actions validate app_topolo_nurture.suppressions.list --data @payload.json --json
topolo actions plan app_topolo_nurture.suppressions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.suppressions.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.suppressions.list",
    "input": {
      "id": "nct_e5477c912eff49b8949f71490c2ded25"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "contactId": "nct_e5477c912eff49b8949f71490c2ded25",
  "blocks": [
    {
      "code": "complaint",
      "purpose": "marketing",
      "scope": "address",
      "since": "2026-10-04T00:32:36.440Z",
      "sourceApp": "app_topolo_nurture"
    },
    {
      "code": "complaint",
      "purpose": "outreach",
      "scope": "address",
      "since": "2026-10-04T00:32:36.440Z",
      "sourceApp": "app_topolo_nurture"
    },
    {
      "code": "manual_block",
      "purpose": "all",
      "scope": "contact",
      "since": "2026-10-04T00:32:36.431Z",
      "sourceApp": "app_topolo_nurture"
    },
    {
      "code": "wrong_person",
      "purpose": "all",
      "scope": "address",
      "since": "2026-10-04T00:32:36.432Z",
      "sourceApp": "app_topolo_nurture"
    }
  ],
  "events": [
    {
      "idempotencyKey": "led_31f7bd15d24f4642b9d56091ae41c9f2",
      "type": "manual_block",
      "scope": "contact",
      "occurredAt": "2026-10-04T00:32:36.431Z",
      "sourceApp": "app_topolo_nurture",
      "reason": "asked",
      "evidenceKinds": []
    },
    {
      "idempotencyKey": "led_9cbd432b0d1b4a9abe41aeea252a909d",
      "type": "wrong_person",
      "scope": "address",
      "occurredAt": "2026-10-04T00:32:36.432Z",
      "sourceApp": "app_topolo_nurture",
      "reason": null,
      "evidenceKinds": []
    },
    {
      "idempotencyKey": "led_f9befe6170df40a68a658da668ba1b2a",
      "type": "complaint",
      "scope": "address",
      "occurredAt": "2026-10-04T00:32:36.440Z",
      "sourceApp": "app_topolo_nurture",
      "reason": null,
      "evidenceKinds": []
    }
  ]
}

HTTP 200. Confirm $.contactId equals the requested contact; blocks[] empty means nothing suppresses the contact.

Another supported 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_cf309c49904648388068eaed4a5c48db"
}

CLI:

topolo actions validate app_topolo_nurture.suppressions.list --data @payload.json --json
topolo actions plan app_topolo_nurture.suppressions.list --resource-type workspace --resource-id "$NURTURE_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_nurture.suppressions.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.suppressions.list",
    "input": {
      "id": "nct_cf309c49904648388068eaed4a5c48db"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "contactId": "nct_cf309c49904648388068eaed4a5c48db",
  "blocks": [
    {
      "code": "complaint",
      "purpose": "marketing",
      "scope": "address",
      "since": "2026-10-04T00:32:36.631Z",
      "sourceApp": "app_topolo_nurture"
    },
    {
      "code": "complaint",
      "purpose": "outreach",
      "scope": "address",
      "since": "2026-10-04T00:32:36.631Z",
      "sourceApp": "app_topolo_nurture"
    },
    {
      "code": "erased",
      "purpose": "all",
      "scope": "address",
      "since": "2026-10-04T00:32:36.705Z",
      "sourceApp": "app_topolo_nurture"
    }
  ],
  "events": [
    {
      "idempotencyKey": "led_ed72c6cedb104599bce3b25d3eec8f24",
      "type": "complaint",
      "scope": "address",
      "occurredAt": "2026-10-04T00:32:36.631Z",
      "sourceApp": "app_topolo_nurture",
      "reason": null,
      "evidenceKinds": []
    },
    {
      "idempotencyKey": "erased:nct_bd24766c41e8448a9620edffd8a208f7",
      "type": "erased",
      "scope": "address",
      "occurredAt": "2026-10-04T00:32:36.705Z",
      "sourceApp": "app_topolo_nurture",
      "reason": "contact_erased",
      "evidenceKinds": []
    }
  ]
}

HTTP 200. Confirm $.contactId equals the requested contact; blocks[] empty means nothing suppresses the contact.

Refused request · not_found

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_d6dce1df14ce45e6af6c01277b01fe8f"
}

CLI:

topolo actions validate app_topolo_nurture.suppressions.list --data @payload.json --json
topolo actions plan app_topolo_nurture.suppressions.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; blocks[] empty means nothing suppresses the contact.

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.

  • Record suppression event: Append one event to the contact's suppression ledger. Blocking events: unsubscribed (all marketing, or one topic with topicKey), hard_bounce, complaint, wrong_person (these three apply org-wide to the address), reply_stop, not_interested (outreach), manual_block (everything). Loosening events need evidence: deliverable (clears hard_bounce) needs verification; repermissioned (clears unsubscribed, reply_stop, not_interested) needs consent_decision, and clearing a complaint also needs verification; manual_unblock (clears manual_block) is an operator action. import_attestation never lifts a block. double_opt_in evidence cannot be sent here; it is produced only by the public confirmation link.

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.