The next step in the application process is creating an application draft (or stub application) where you store the further information of the application before you finally submit it. You’ll need the jobDbId of the job and an user access token to authenticate as the applicant.

HTTP-Method

POST

Path

/api/rest/v3/frontend/applications

Authentification

User Access Token

Path Parameter

-none-

Query Parameter

jobDbId

Responses

Action	Response	Description
success	applicationId	The ID of the draft application for further use
error	400 – { “code”: “invalid_job_id”, “message”: “Invalid jobId” }	JobDbId does not exist
error	404 – JobPosting not found for jobId X	There is no job posting for this job
error	403 – JobPosting not accessible for jobId X	The applicant has no access to the job posting (for example because the job has been posted to the internal channel but the applicant is no internal applicant)
error	410 – JobPosting inactive for jobId X	The jobposting has been deactivated
error	400 – { “code”: “project_not_applicable”, “message”: “Invalid jobposting id” }	The jobposting is invalid
error	400 – { “code”: “project_not_applicable”, “message”: “Application for this project already exists. The application can not be changed anymore.” }	See message part
error	400 – { “code”: “project_not_applicable”, “message”: “Application for this project already exists. The application can be changed though.” }	See message part
error	400 – { “code”: “project_not_applicable”, “message”: “Applications for this project are not possible. Maybe the job was closed in the meanwhile or is not available for other reasons.” }	See message part
authorization error	401 / 403	See here and here for details.

Example call with curl and user access token

Response:

Example call with curl and user access token

Example error case where an application for that applicant and job already exists

Antwort: