Find a submission ID and read assessment scores and hiring decisions.

Submissions

Read assessment results after a candidate submits. An interview's completed status does not indicate whether the candidate submitted or grading finished.

Read assessment results

GET /api/v1/submissions/{id} · Required scope: submissions:read.

Use a submission ID from the dashboard or MCP. invite_id and interview.id are not submission IDs. REST currently has no endpoint to list submissions or resolve a submission ID from an invite.

bash

curl --fail-with-body https://litmushiring.com/api/v1/submissions/sub_def456 \
  -H "Authorization: Bearer $LITMUS_API_KEY"

Returns:

json

{
  "id": "sub_def456",
  "assessment_id": "asmt_ghi789",
  "candidate": { "email": "candidate@example.com", "name": "Sample Candidate" },
  "score": 84,
  "native_score": 4.2,
  "score_scale": { "min": 0, "max": 5 },
  "decision": "advance",
  "submitted_at": "2026-05-26T12:00:00.000Z",
  "report_url": "https://litmushiring.com/company/reports/sub_def456"
}

Field	Description
`native_score`	Score on a 0.0–5.0 scale. Use this for new integrations.
`score`	Score on the legacy 0–100 scale, retained for existing integrations.
`score_scale`	The range of `native_score`, or `null` when that score is unavailable.
`decision`	`pending`, `advance`, or `reject`. Defaults to `pending` until a reviewer records a decision.
`report_url`	Dashboard report URL. Requires a signed-in organization member.

Both scores are null until a report is available. native_score is also null for reports graded before the 0–5 scale was introduced.

Find a submission's id

Use the submission ID from the dashboard report URL, /company/reports/{submission_id}, or call the MCP list_submissions tool with a key that has submissions:read. See the MCP tool reference.

report_url opens the report in the dashboard and requires a signed-in member of the organization. Poll the submission endpoint to detect a completed report or a reviewer decision. See Webhooks.