Documentation pages
GET/reviews/{reviewId}/result

Key permission: reviews:read

Get the result

What to send

The review ID in the URL, plus your API-key header, after its status becomes completed. No request body.

What you get back

The finished review as structured JSON—not a PDF or an embedded score card. You can store the result or display its scores and findings in your own application.

decisionstring
ready: ready to use. needs_fixes: required corrections. human_review: human review is needed.
scoresobject
accuracyQuality and coverage, each from 0 to 100.
findingsobject[]
Each finding has id, type, title and evidence. Types are required, improvement and strength. Location, page, question context, category and suggestedAction are included when available.
reportobject
The full report structure used by the Steletta interface, with verdict, both score axes and grouped findings.

The response also includes the review ID, completion timestamp and version fields. Your integration should accept additional response fields. 409 means the review is not complete; 410 means the saved result expired or was removed.

Request example
curl --fail-with-body -X GET 'https://www.steletta.com/api/v1/reviews/rev_example/result' \
  -H "Authorization: Bearer $STELETTA_API_KEY"
Example response · Illustrative result (excerpt)
{
  "reviewId": "rev_example",
  "decision": "needs_fixes",
  "scores": {
    "coverage": 92,
    "accuracyQuality": 84
  },
  "findings": [
    {
      "id": "finding_1",
      "type": "required",
      "title": "The answer key is incorrect.",
      "location": "Question 7",
      "page": 2,
      "evidence": "The worked calculation gives 20 W, but the key lists 180 W.",
      "suggestedAction": "Change the answer key for Question 7 to 20 W."
    }
  ]
}