List senders

GET/api/v1/senders
Requires anorganization API keywith the scopesenders:read

Request

GET/api/v1/senders
curl -X GET 'https://app.mailyte.com/api/v1/senders' \
  -H 'Authorization: Bearer mk_live_YOUR_API_KEY'
The key names its own organization, so no X-Organization-ID header is needed.

Response

Success.

  • dataobject
    • dataarray<object>
      • objectstringsender
      • idstring

        Unique identifier for the sender.

      • namestring

        The display name recipients see, e.g. Acme Support in Acme Support <hello@acme.com>.

      • emailstring

        The address this identity sends as. POST /messages refuses a from that is not a verified sender.

      • domainstring

        The domain this address sends from, such as acme.com. Its DNS details are on GET /domains/{domain}.

      • verificationobject

        Whether this address may be sent from. Verification checks the domain's public DNS records; there is no token.

        • statestringpending | verified | failed

          The one verification answer. Only verified permits sending; pending and failed both do not, and differ in whether a check has run.

        • verified_atstring

          When the address last passed verification. Set only while state is verified. Read state to know whether the sender works.

        • errorstring

          Why the last check failed, usually DNS records still missing. Null when state is not failed.

      • created_atstring

        When this sender was created.

      • updated_atstring

        When this sender was last changed.

    • pagination_metaany

Returned inside the standard envelope.

Errors

StatusWhen
401The API key is missing, unknown, revoked or expired. All four answer identically, on purpose: distinguishing them would confirm which keys exist.
403The key is valid but may not do this: it lacks the required scope, its IP allowlist does not include you, or this endpoint does not accept API keys.
404No such resource in this organization.
422The request was understood but the values were not acceptable.
429Too many requests, or the organization has spent its sending allowance. `Retry-After` says how long to wait.

Every status, with what causes it and what to do, is on the error reference.