Get an application's status, data and qualifications
The application as it currently stands: its intake status, the assessment workflow’s status once one is running, the qualifications recorded against it, and the snapshot those qualifications were captured into.
status is the INTAKE status and takes five values:
RECEIVED— stored, waiting to be picked up for assessment.workflowStatusis null.READY— you have told us the supporting documents are adequate. Advisory: an assessment can be started without it.PROCESSING— an assessment has been started.workflowStatussays where it has got to.WITHDRAWN— withdrawn, and not reversible. Reinstating means a new application.FAILED— intake could not be completed.statusDetailsays why.
qualifications is what we hold, in the field names you sent — see
GET /institution/qualification-types for what each type may carry. For the credit decision,
read GET /institution/applications/{id}/outcome.
404 if the id is unknown or belongs to another institution.
Authentication
Paste a Keycloak access token (no "Bearer " prefix)
Path parameters
Response
Your own code for the intake the applicant is starting, e.g. "5269" for Term 3 2026.
Optional, but worth sending: our officers work applications in intake order, and one with no intake cannot be prioritised against the rest.
Send the code rather than the name. These are YOUR term codes, loaded from the intake schedule you supply us, so a code you use is a code we hold; one we do not recognise is refused with a 400 naming it.
Application status: RECEIVED, READY, PROCESSING, WITHDRAWN or FAILED.
Failure detail when status is FAILED; null otherwise.
Assessment workflow status once processed (e.g. DECIDED, CREDIT_TEAM_REVIEW); null while RECEIVED.
Your own unique id for this application, e.g. an application number. Unique per sourceName.
Your own references for this record, one per system you keep it in. A person or an application known by a different id in SITS than elsewhere carries both.
Optional. sourceName and sourceRef still work exactly as before and count
as the FIRST entry here, so nothing you have already built needs to change.
Send both forms and they are combined, with duplicates collapsed.
Order matters: the first entry is the one echoed back as sourceRef, and the
one shown in lists and in the change feed.
