DELETE/api/v1/projects/{project_id}/subscribers/{subscriber_id}
Needs scope: writeMCP tool: erase_subscriber
operationId erase_subscriber
Erase a subscriber
Erases the subscriber for good, on request: its row is deleted, and in
its events (and in the address’s suppression events) the address is
replaced by erased:<hash>, in the background; the erasure itself is
recorded as subscriber.erased. The address’s suppressions stay, so it
gets no mail it had opted out of if it is added again. Needs scope
write; works on a subscriber of a deleted list too. A second call is
404.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
project_idrequired |
path | string · uuid | The project’s id |
subscriber_idrequired |
path | string · uuid | The subscriber’s id |
Request body
None.
Responses
204
The subscriber is erased
No content.
404
No such subscriber (an erased one included) or project, or another project’s (not_found)
429
The key is over its rate limit, api.rate_limit_per_minute requests a minute on this node (rate_limited)
| Header | Type | Description |
|---|---|---|
Retry-After | integer | Seconds until the key’s next request passes; rounded up. |
504
Postwind’s storage did not answer within its time limit (storage_timeout). A change the request makes may still take effect: check before repeating it. A repeat with the same Idempotency-Key never runs it twice: it is 409 idempotency_key_in_progress until the key’s 24 h end