Skip to main content
POST
Cancel a Subscriber Operation
Stop future work while retaining completed changes. See background contact tasks for selection, retry and cancellation behavior. Requires subscribers:read. Tagging and cancelling a tagging task also require subscribers:tag; creating tag definitions requires tags:write; triggering automations requires automations:trigger. Personal keys retain current company role restrictions. Company keys retain company-scoped authority. Workers recheck authority on every page. Cancellation returns 200 with the terminal operation. Applied tags remain. A contact being updated when cancellation wins is recorded in failures with an uncertain outcome; check it before starting another task. Repeating cancellation returns the same terminal state. A busy cancellation race returns 409 and can be retried. Missing authentication returns 401; missing scopes or company access return 403. An operation outside the selected company is reported as 404, as is an operation whose retained record no longer exists.