{
"report_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"subject_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
"doc_id": "12983319",
"country": "CL",
"subject_type": "person",
"score": 742,
"band": "B",
"verify_code": "Q3fa85f6457174562b3fc2c963f66afa6a1b2c3d4e5f"
}Qscore credit report ready
A Qscore credit report purchased with POST /v1/qscore/reports finished generating successfully. The payload carries the report identity, the resulting score/band and the public verify_code (shareable with the subject as proof of authenticity at GET /verify/qscore/{code}). If the generation fails the report shows status: failed and no event is emitted. The event is also emitted when the purchased report was already available for the subject (idempotent reuse).
The same event fires for a SELF report generated by the account holder with POST /v1/qscore/my-report; in that case the payload adds purpose: "self_access" (absent for purchased reports).
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.
{
"report_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"subject_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
"doc_id": "12983319",
"country": "CL",
"subject_type": "person",
"score": 742,
"band": "B",
"verify_code": "Q3fa85f6457174562b3fc2c963f66afa6a1b2c3d4e5f"
}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.