Applying for a job posting

This method either gets an exisiting application or creates a new one, its endpoint is /jobs/{jobDbId}/apply:

with TOKEN being user access token, note that in contrast to most of the functionality in the job API, a client client access token is not sufficient. The {jobDbId} corresponds to the ID of the job in the database, the {creationMode} defines how the new application is to be created, You find more details below.

The system attempts to localize the resulting ApplicationData using information from the header. In the curl example you can manipulate the header by adding -H “Accept-Language:{locale}”, whereat locale can be en, de and so on.

Path parameters

Name Description Data Type
jobDbId The ID of the job in the jobs database. String

Query parameters

Name Description Data Type Default Value
trackerId Used to remember the user through multiple applications. Currently not used! String empty string
creationMode How to create a new application, if necessary. Must be either CREATE_EMPTY, CREATE_COPY or CREATE_COPY_ATTACHMENTS. String n/a

Response values

Upon Returned value Description
success JSON-encoded ApplicationData-object the application
error 400 – BAD REQUEST The given Job ID is invalid or the user applied to the position before.
authorization error 401 / 403 See here for details.

Example return value

Comments

Comments are closed.