Say an application's supporting documents are adequate
Moves a RECEIVED application to READY: you have the documents you need and it is workable. ADVISORY — an assessment can be started without it, and an application left in RECEIVED is not stranded. Safe to retry: calling this on an application already READY returns it unchanged rather than failing. 404 if the application is unknown, 409 if it has moved past RECEIVED.
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.
