Get report evidence
Retrieve the versioned resume evaluation for an evidence-based review in your application. This includes rubric findings, supporting evidence, gaps, and follow-up questions.
Before you call
Use reports:read and schemaVersion=1 (the default). Wait for a completed report or a report.result_ready event.
Required scope: reports:read.
What happens next
Save resultRevision with the resource and attempt IDs. Read scoreScale, limitations, and evidence before displaying a score. A pending or failed report has result=null. Text and lists are bounded.
Recovery
RESULT_VERSION_UNSUPPORTED means request a supported schema version. Missing measurements are unknown, not zero. A 404 after a deletion event is expected; stop polling that resource.
Follow the complete workflow · Errors and retries
ApiKeyAuthorizationBearer <token>id*stringResource ID returned by this resource's creation or list endpoint. See prerequisites for whether this is a report, interview, job, or batch ID.
1 <= length <= 100schemaVersion?stringPublic payload format version. Result requests currently support 1; this is independent of the assigned product version.
"1"Save resultRevision with the resource and attempt IDs. Read scoreScale, limitations, and evidence before displaying a score. A pending or failed report has result=null. Text and lists are bounded.
application/json- response
data*# Set PROBB_URL and PROBB_API_KEY. Replace RESOURCE_ID if present.curl --fail-with-body -X GET "$PROBB_URL/api/v1/reports/RESOURCE_ID/result" \ -H "Authorization: Bearer $PROBB_API_KEY"{ "data": { "schemaVersion": 1, "reportId": "report_example", "attemptId": "attempt_example", "reportSystemVersion": "assigned-report-version", "resultRevision": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", "publishedAt": "2026-09-29T12:00:00.000Z", "status": "completed", "code": null, "externalReference": { "source": "my-ats", "id": "application-42" }, "result": { "scoreScale": { "minimum": 0, "maximum": 10 }, "score": 8, "summary": "Relevant backend delivery experience; validate incident response depth.", "scoreReasoning": "Strong API and database evidence, with limited detail on production incidents.", "humanReviewRecommendation": "Validate operational experience in an interview.", "rubric": [ { "key": "backend", "label": "Backend delivery", "status": "positive", "score": 8, "analysis": "Relevant API delivery experience.", "evidence": [ "Built and maintained a PostgreSQL-backed API." ], "gaps": [ "Incident response ownership is not described." ] } ], "highlights": [ { "category": "technicalCore", "label": "API development", "status": "positive", "summary": "Relevant delivery evidence." } ], "followUpQuestions": { "technical": [ "Describe a database performance investigation." ], "clarification": [ "What was your role in production support?" ], "riskReview": [] }, "integrity": { "riskLevel": "low", "summary": "No conflicting identity evidence in this synthetic example.", "signals": [] }, "policyWarnings": [], "ignoredCriteria": [] } }}