Finalise a submission after required documents have been uploaded
POST
/api/submissions/{submission_id}/submit
Submissions
Last modified:2026-07-27 09:06:51
Maintainer:Not configured
Final submission step for a form that required document upload. Internally routed to the same handler as the legacy POST /api/submit-form/{submission_ref} endpoint - this path just also accepts the raw submission_id instead of requiring the generated submission_ref (which does not exist yet for a still-pending, docs-required submission). Rejects with 403 'You must upload the requested documents before you can submit the form' if documents are still required at call time. Also rejects with 403 'Form already submitted' for any submission that never required document upload in the first place (those are finalised immediately at creation), so in practice this endpoint is only ever usefully callable for submissions that came back from creation with docs_required=true. On success: marks the submission as fully submitted, generates and stores its submission_ref, updates the candidate record, and sends the completion notification email (with any uploaded documents attached, subject to max_attachment_size).
Request
Authorization
API Key
Add parameter in header
API-KEY
Example:
API-KEY: ********************
or
Path Params
Header Params
Responses
🟢200
application/json
Submission finalised and notification email sent. The response body is an array containing a single empty string, matching this controller's existing convention for no-content success responses.
Bodyapplication/json
🟠403
🟠401Unauthorised
🟠404SubmissionNotFound
Request Request Example
Shell
JavaScript
Java
Swift
curl--location--request POST '/api/submissions//submit' \
--header'API-VERSION;' \
--header'API-KEY: <api-key>'