topics
Delete a subscription topic
DELETE /v1/topics/{name}
Auth required
api.topics.manage
Deletes a managed topic definition and drops it from the SES contact
list. The topic is addressed by its immutable name. Git-backed topics
are read-only here (409 conflict) — the sync owns them, and removing
the name from the repo archives (never deletes) the topic. Idempotent:
deleting an already-absent topic returns 204.
Path parameters
name string required The topic's org-unique name (the same identifier GET /v1/topics exposes). An unknown name is 404 not_found.
Responses
204 Topic deleted (no content)
401 Missing, malformed, or unknown API key application/problem+json
403 Key lacks the required scope or plan limit violated application/problem+json
409 The mutation is rejected by a state rule rather than a bad request — e.g.
editing a git-backed (read-only) definition. The
code is conflict.
application/problem+json 429 Per-org rate limit exceeded application/problem+json
500 Unexpected server-side failure. The
code is internal_error. The
request_id field can be quoted to SendOps support to investigate.
application/problem+json