Skip to main content
POST
Refresh Account Health
Recomputes the account’s health score from scratch and stores a new snapshot. This is a rule-based calculation, not an AI call — it scores 9 fixed factors (pipeline health, communication recency, contact breadth, contact engagement spread, meeting cadence, deal pipeline value, deal win rate, task follow-through, new-deal recency) against data pulled live from deals, activities, contacts, and open tasks for this account, starting from a base of 50 and clamping the result to 0100. trend compares the new score to the account’s snapshot from ~30 days ago (falling back to the oldest available snapshot if the account has less than 30 days of history): improving if the score rose by more than 3 points, declining if it fell by more than 3, otherwise stable. On an account’s first-ever refresh (no prior snapshot at all), trend is always stable. As a side effect, this also writes the new score onto accounts.health_score (the denormalized column returned by List Accounts and Update an Account) — but that write is best-effort: if it fails, the refresh still returns 200 with the freshly computed score, it just doesn’t get reflected on the account row.

Auth

Requires a CRM manage scope and an active organization on the token. Any *:manage scope qualifies — in practice contacts:manage, deals:manage, companies:manage, or activities:manage.

Response

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

account_id
string
required

The account's id.

Response

Successful Response