Qscore batch scoring completed
A batch scoring job created with POST /v1/qscore/batches finished processing all of its items. This is the single completion signal of the batch: the individual reports do not emit their own risk_report_ready webhook (and no per-item email is sent). status is completed when every item succeeded, completed_with_errors when at least one item failed terminally (its fee was refunded) and failed when the batch itself could not be processed. The counters always add up: succeeded_items + failed_items = total_items. Read the per-item results with GET /v1/qscore/batches/{id}/items or download them with GET /v1/qscore/batches/{id}/results.csv.
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
Response
Return any 2xx to acknowledge the delivery.