Read report evidence
Choose summary, status, or detailed results and interpret missing evidence correctly.
Use the report APIs to bring a completed resume evaluation into your application. All three reads require reports:read.
| Endpoint | Use it for |
|---|---|
| Get report status | Lightweight polling and current attempt identity |
| Get a report summary | Candidate/job context and a compact result |
| Get report evidence | Versioned rubric, supporting evidence, gaps, and follow-up questions |
Retrieve a versioned report
GET /api/v1/reports/{id}/result?schemaVersion=1 requires reports:read. The response contains the report/analysis attempt, product version, result revision, publication time where available, status, and public evidence. Resume scores use a 0–10 scale. A pending or failed analysis has result: null. Unsupported versions return RESULT_VERSION_UNSUPPORTED; never interpret them as a zero score.
Rubric evidence, gaps, highlights, integrity signals, follow-up questions, and policy limitations are selected explicitly. Detailed text is bounded to 4,000 characters per field; lists are bounded. Original documents, private prompts, and internal provider data are not exposed. Results support human review and do not make a hiring decision for you.
curl --fail-with-body "$PROBB_URL/api/v1/reports/$REPORT_ID/result?schemaVersion=1" \
-H "Authorization: Bearer $PROBB_API_KEY"Decide what to display
Wait for status=completed and a non-null result. Show summary and score reasoning together; make rubric evidence, gaps, and integrity review accessible. Preserve null for missing measurements. Empty lists are not proof there are no risks.
requires_action means an authorised reviewer must inspect the mismatch in the app. failed is a processing outcome, not a candidate assessment. UNSUPPORTED_REPORT_VERSION or RESULT_UNAVAILABLE should produce an unavailable state in your UI, not an invented score.
Keep a result synchronized
Store report ID, attempt ID, schema version, and result revision. On report.result_ready, retrieve the current publication; deduplicate repeated revisions. A delayed event may describe an older attempt. On report.deleted, stop polling and apply your system's deletion policy. A subsequent 404 is expected.
See API concepts for the distinction between the public schema and assigned configuration. Interview evidence has its own workflow.