DELETE · Email
List, create or delete email forwarders
List, create or delete email forwarders
DELETE
/api/v1/email/forwarders
Description
action=list returns each forwarder address and its destinations. action=create needs address and destinations[]; action=delete needs address. Creating and deleting require the write:email scope.
Query parameters
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response. Up to 255 characters.
|
action
required
|
enum |
list all forwarders, create a new one, or delete one. create and delete require the write:email scope. One of list, create, delete.
|
address
|
string |
Up to 254 characters. Pattern ^[a-zA-Z0-9._%+-]+(@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,})?$.
|
destinations[]
|
string[] |
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.
400
401
No token was presented, or the token is revoked, expired or unknown.
403
The token lacks a required scope, or this account does not own the resource.
404
No such resource for this account.
422
Validation error
429
The rate limit for this token is exhausted. See `Retry-After`.
500
Something went wrong on our side. The failure is logged against `requestId`.