Qscore monitoring alert
A subject the account monitors via PUT /v1/qscore/subjects/{docID}/monitoring changed since the last check. triggers lists what fired the alert: score_drop_below (the score crossed the subscription’s monitor_since_score threshold downward: previous >= threshold, new < threshold), new_records (the bureau registered new events; with only_material: true only materially negative events — open delinquency, protest, bankruptcy, lawsuit — count) or records_removed (the bureau now shows fewer events than the baseline, i.e. a record was closed or deleted). Active subscriptions are re-checked every ~5 minutes; the first pass after subscribing only seeds the baseline and never alerts on the history the purchased report already showed. score and previous_score are omitted while the subject has no classifiable score, and new_records is omitted when no new event fired.
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.
Authorizations
Session JWT (from register/login) or API key (pk_...).
X-API-Key: <token> is accepted as an alternative header.
Body
person, company score_drop_below, new_records, records_removed A, B, C, D, E, SC Response
Return any 2xx to acknowledge the delivery.