Bulk Verify (domain)
POST
/api/v1/domains/bulk-verifyRequest
POST
/api/v1/domains/bulk-verifycurl -X POST 'https://app.mailyte.com/api/v1/domains/bulk-verify' \
-H 'Authorization: Bearer mk_live_YOUR_API_KEY'const response = await fetch('https://app.mailyte.com/api/v1/domains/bulk-verify', {
method: 'POST',
headers: {
Authorization: 'Bearer mk_live_YOUR_API_KEY',
},
});
const { data } = await response.json();import requests
response = requests.post(
"https://app.mailyte.com/api/v1/domains/bulk-verify",
headers={"Authorization": "Bearer mk_live_YOUR_API_KEY"},
)
data = response.json()["data"]<?php
$response = Http::withToken('mk_live_YOUR_API_KEY')
->post('https://app.mailyte.com/api/v1/domains/bulk-verify');
$data = $response->json('data');require "net/http"
require "json"
uri = URI("https://app.mailyte.com/api/v1/domains/bulk-verify")
request = Net::HTTP::Post.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.
dataobjectobjectstringbulk_resultactionstringverify | delete | activate | suspendWhat was attempted against every id.
requestedintegerHow many ids were submitted.
succeededintegerfailedintegerresultsarray<object>Every submitted id with its own outcome, in submission order. A bulk call is partial by nature: `succeeded` and `failed` both being non-zero is an ordinary result, not an error.
idstringThe domain id as submitted. Null on a failure the operation could not attribute to one.
statusstringsucceeded | failederrorstringWhy this one failed. Null when it succeeded.
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.