List senders
/api/v1/sendersRequest
/api/v1/senderscurl -X GET 'https://app.mailyte.com/api/v1/senders' \
-H 'Authorization: Bearer mk_live_YOUR_API_KEY'const response = await fetch('https://app.mailyte.com/api/v1/senders', {
method: 'GET',
headers: {
Authorization: 'Bearer mk_live_YOUR_API_KEY',
},
});
const { data } = await response.json();import requests
response = requests.get(
"https://app.mailyte.com/api/v1/senders",
headers={"Authorization": "Bearer mk_live_YOUR_API_KEY"},
)
data = response.json()["data"]<?php
$response = Http::withToken('mk_live_YOUR_API_KEY')
->get('https://app.mailyte.com/api/v1/senders');
$data = $response->json('data');require "net/http"
require "json"
uri = URI("https://app.mailyte.com/api/v1/senders")
request = Net::HTTP::Get.new(uri)
request["Authorization"] = "Bearer mk_live_YOUR_API_KEY"
response = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(request) }Response
Success.
dataobjectdataarray<object>objectstringsenderidstringUnique identifier for the sender.
namestringThe display name recipients see, e.g.
Acme SupportinAcme Support <hello@acme.com>.emailstringThe address this identity sends as.
POST /messagesrefuses afromthat is not a verified sender.domainstringThe domain this address sends from, such as
acme.com. Its DNS details are onGET /domains/{domain}.verificationobjectWhether this address may be sent from. Verification checks the domain's public DNS records; there is no token.
statestringpending | verified | failedThe one verification answer. Only
verifiedpermits sending;pendingandfailedboth do not, and differ in whether a check has run.verified_atstringWhen the address last passed verification. Set only while
stateisverified. Readstateto know whether the sender works.errorstringWhy the last check failed, usually DNS records still missing. Null when
stateis notfailed.
created_atstringWhen this sender was created.
updated_atstringWhen this sender was last changed.
pagination_metaany
Returned inside the standard envelope.
Errors
| Status | When |
|---|---|
401 | The API key is missing, unknown, revoked or expired. All four answer identically, on purpose: distinguishing them would confirm which keys exist. |
403 | The 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. |
404 | No such resource in this organization. |
422 | The request was understood but the values were not acceptable. |
429 | Too 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.