After creating an draft application in the step before you can continue adding information to that stub with the help of the application ID you got from there. Please stick to the format of the ApplicationProfileDTO. Please consider that the current state of that DTO replaces the currently stored state of the DTO. To add attachments you can use another endpoint. Besides the DTO you need an user access token to authenticate.






User Access Token

Path Parameter


Query Parameter





Action Response Description
success 204 – no content
error 400 – { “code”: “application_access_error”, “message”: “Invalid application data” } ApplicationProfileDTO was nut submitted
error 400 – { “code”: “application_access_error”, “message”: “Application does not exist” } No application was found for the provided ID or the applicant does not own it.
authorization error 401 / 403 See here and here for details.

Example call with curl and user access token


The JSON object that is submitted instead of the SEE_BELOW placeholder in the above example. The comments here are just present for explanatory reasons.

The fields commented with “Resolved catalog value” have to be filled from catalogs. Please read here how you can get all possible values of a catalog in each language. Please always use the job language or else the storing wont work.

So if you want to make it possible to fill these fields in your application form, you have to provide the applicant the list of possible values and then provide only one value back to the API. If you submit values that are not in the job language, they wont be stored. Thats similar as with the mandatory prescreening questions of a job. You first request all questions from the respective endpoint. If a question has a answer catalog, you present the possible values to the applicant and submit the clear text answer to the API.
In the experiences, educations and languages you may submit lists of catalog values.


Comments are closed.