Get DKIM state (or attempt to enable it)

PUT


          /api/v1/email/dkim

Try it

W Write

Scope write:email

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

The GET route returns enabled and, when published, the record {name, value} for the _domainkey public key. Enabling or regenerating DKIM is not available on this node.

Body

Send as application/json.

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.

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.

400

invalid_request

401 No token was presented, or the token is revoked, expired or unknown.

unauthorizedtoken_expiredtoken_revoked

403 The token lacks a required scope, or this account does not own the resource.

insufficient_scopedomain_not_owned

404 No such resource for this account.

not_foundmailbox_not_found

422 Validation error

validation_failed

429 The rate limit for this token is exhausted. See `Retry-After`.

rate_limited

500 Something went wrong on our side. The failure is logged against `requestId`.

internal_error

Description

Body

Responses

Commonly returned errors

Related endpoints