Triggers an async re-check of the SPF, DMARC, and MX DNS records for the campaign's sending domain, and polls the result of a previously queued refresh.
Two-phase usage
Phase 1 – Trigger a refresh
Send a PATCH request without a refresh_id body parameter. Mailivery will queue the DNS check job and return a 202 with an encrypted refresh_id token.
Phase 2 – Poll the result
Repeat the same PATCH request, this time including the refresh_id from Phase 1. Poll at a reasonable interval (e.g. every 3–5 seconds) until the response code is REFRESH_DNS_COMPLETED or an error is returned.
Rate limiting
Each campaign domain may only trigger a new refresh once every 30 minutes. Subsequent trigger requests within that window return 429 TOO_MANY_REQUESTS. Polling an existing refresh_id is not rate-limited.