Push Subscriptions Delete

Outcome

Deletes the caller’s stored push endpoint registration.

Before you start

• Verify the intended environment, authenticated identity and explicitly authorized ownership context.
• Discover the published notifications:write permission and any required resource grant.
• Approve the actual effects before confirming the unchanged planned request. Fixture identifiers, recipients and provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_one.push_subscriptions.delete --detail --json

• endpoint: Actual browser push endpoint owned by the caller; never reuse fixture endpoints.

Request

DELETE /api/push/subscriptions

Inspect and test this action.

Input fields

Inspect nested fields.

Interpret the response

Inspect success and deletedCount. Zero means no matching registration was deleted; it does not prove that no previously queued notification can arrive.

Inspect the declared output schema and captured variants.

Worked examples

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.

Save the reviewed input below as payload.json; substitute discovered identifiers and bind credential/resource context separately. CLI:

topolo actions validate app_topolo_one.push_subscriptions.delete --data @payload.json --json
topolo actions plan app_topolo_one.push_subscriptions.delete --data @payload.json --json
topolo actions call app_topolo_one.push_subscriptions.delete --data @payload.json --confirm --detail --json

MCP planning and execution use the same reviewed input:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_one.push_subscriptions.delete",
    "input": {
      "endpoint": "https://push.example.com/abc"
    }
  }
}

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_one.push_subscriptions.delete",
    "input": {
      "endpoint": "https://push.example.com/abc"
    },
    "confirm": true,
    "detail": true
  }
}

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "endpoint": "https://push.example.com/abc"
}

Captured response:

{
  "error": "Token validation failed"
}

Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

Successful response · HTTP 200

Input · payload.json:

{
  "endpoint": "https://push.example.com/abc"
}

Captured response:

{
  "success": true,
  "message": "Push subscription deleted successfully",
  "deletedCount": 1
}

Inspect success and deletedCount. Zero means no matching registration was deleted; it does not prove that no previously queued notification can arrive.

Verify the result

• Inspect success and deletedCount. Zero means no matching registration was deleted; it does not prove that no previously queued notification can arrive.

Errors and recovery

• auth_error (HTTP 401): Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

These are observed local refusals; inspect the raw error body because one SDK code can represent several handler messages. Preserve the request id when available.

Recovery boundary

Register the actual current browser subscription again after obtaining its permission and fresh endpoint keys.

Related actions

• Push Subscriptions Create: Register a browser push subscription for the caller, so TopoloOne can send them notifications.

Evidence

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.