Refresh setup score
Re-resolve DNS and return the refreshed setup score
Synchronously re-runs the SPF/DKIM/DMARC/MX lookups, persists the records, and returns the recomputed score. A record whose lookup failed at the resolver is left untouched rather than recorded as failing, so a resolver blip does not depress the score; a record that has never resolved at all reads unknown.
curl -X POST "https://lynx-api.trulyinbox.com/v2/workspaces/0/accounts/0/setup-score/refresh"{
"data": {
"accountId": 456,
"emailAddress": "john@acme.com",
"score": 82,
"band": "green",
"items": [
{
"key": "spf",
"label": "SPF record",
"score": 29,
"maxScore": 29,
"indeterminate": true
}
],
"dnsCheckedAt": "2019-08-24T14:15:22Z"
},
"meta": {
"request_id": "req_2f1c…",
"timestamp": "2019-08-24T14:15:22Z"
}
}{
"error": {
"code": "invalid_request",
"message": "string",
"details": {},
"retry_after": 34
},
"meta": {
"request_id": "req_2f1c…",
"timestamp": "2019-08-24T14:15:22Z"
}
}{
"error": {
"code": "invalid_request",
"message": "string",
"details": {},
"retry_after": 34
},
"meta": {
"request_id": "req_2f1c…",
"timestamp": "2019-08-24T14:15:22Z"
}
}Get setup scoreGET
Get the setup health score for an account A checklist of SPF, DKIM, DMARC, MX, sender name, and warmup-started, plus the whole-percent share of them that pass. DKIM is skipped for a personal-domain mailbox (scored out of 5 instead of 6). DMARC is informational - it reads `warning` when absent and does not count toward the score. Served from the cached DNS health row; POST .../setup-score/refresh to re-resolve first.
Get deliverability insightsGET
Per-account deliverability insights