Check email account health score

Every email account you send from has a health score from 0 to 100: the share of its warm-up emails over the last 7 full days that landed in the inbox rather than spam. It is the same number the app shows, and the API gives it to you for every account in one call.

Read every account's score in one request

curl "https://api.emailchaser.com/r/sender-emails?limit=200" \
  -H "Authorization: Bearer $EMAILCHASER_API_KEY"

{
  "senderEmails": [
    {
      "id": 4321,
      "address": "jane@acme-outreach.com",
      "isConnected": true,
      "healthScore": 96,
      "currentDailyLimit": 30,
      "campaignIds": [1234]
    }
  ],
  "total": 12,
  "page": 1,
  "limit": 200,
  "hasMore": false
}

For one account, call GET /sender-emails/{id}. Add ?campaignId=1234 to the list to see only the accounts a campaign sends from.

Here is how to read the score

The score moves every day as warm-up emails land in the inbox (up) or in spam (down), so check the trend rather than one reading.

See the warm-up behind the score

GET /sender-emails/{id}/warmup returns the same healthScore with the warm-up settings that drive it: whether warm-up is enabled, today's target (currentPerDay), the daily cap (capLimit) and the ramp (startLimit, increaseBy). Change them with PUT /sender-emails/{id}/warmup.

Let campaigns skip weak accounts on their own

Set minimumHealthScore (1 to 100) on a campaign with PUT /campaigns/{id}, and the campaign holds back any account below that score, or without one, until it recovers. Its conversations wait for that account rather than moving to another. Send 0 to remove the minimum. GET /campaigns/{id} shows which accounts the minimum is holding back.

Measure where your emails really land with Inbox Placement

The health score comes from warm-up. With the Inbox Placement add-on, GET /inbox-placement/sender-reputation also gives each account a reputation score from real placement tests across Gmail, Outlook and Yahoo (-1 when it hasn't been measured). Without the add-on that endpoint answers 403.