GET · DNS zones & records
List the MX (mail) templates for a zone
List the MX (mail) templates for a zone
/api/v1/dns/zone/mx-templates
This scope is inferred from the method and the endpoint's group — the OpenAPI document does
not carry one per operation. The wire is authoritative; whoami reports what your
token actually holds.
Description
Returns {templates:[{key,name,description,records[]}], currentMx[]} for the resolved domain. To apply one, call manage_dns_zone with action=mx-template and a template key — that is confirmation-tier and changes nothing until a human approves.
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.
|
Responses
A 200 response returns the shape shown in the rail.
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.