{
  "subject_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
  "report_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "old_score": 742,
  "new_score": 688,
  "old_band": "B",
  "new_band": "B"
}

Qscore score changed

A newly generated Qscore report produced a score different from the subject’s previous known score (e.g. on a monitoring re-pull or a new purchase). Emitted only when the score actually changes; the payload carries the old and new score/band pair so you can decide whether to act. Subscribe to this event to monitor a subject over time without polling.

Every delivery includes X-Webhook-Event, X-Webhook-Event-ID, X-Webhook-Delivery-ID, X-Webhook-Timestamp and X-Webhook-Signature = hex(HMAC-SHA256(secret, timestamp + "." + body)). Respond 2xx; up to 5 attempts with incremental backoff.

WEBHOOK

risk_score_changed

{
  "subject_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
  "report_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "old_score": 742,
  "new_score": 688,
  "old_band": "B",
  "new_band": "B"
}

Authorizations

Authorization

string

header

required

Session JWT (from register/login) or API key (pk_...). X-API-Key: <token> is accepted as an alternative header.

Body

application/json

subject_id

string

report_id

string

old_score

integer

new_score

integer

old_band

string

new_band

string

Response

200

Return any 2xx to acknowledge the delivery.