Applicant and Jobs
Before you start the appliction process you can check if an applicant already applied to a job opening and what the ID of this application would be. There is a strict limitation that there can only be one application per job and and applicant, even an application has been withdrawn. For both descriped request you require the jobDbId of the job a user access token for the applicant account that you can generate as described her.
Did the applicant already apply for the job?
HTTP-Method
GET
Path
/api/rest/v3/frontend/jobs/{jobDbId}/applied
Authentification
User Access Token
Path Parameter
jobDbId
Query Parameter
-none-
Responses
Action | Response | Description |
---|---|---|
success | true or false | |
error | 404 – JobPosting not fount 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 | 404 – { “code”: “get_project_error”, “message”: “Project for jobId X not available” } | There is no job for this jobDbId |
error | 404 – { “code”: “get_project_error”, “message”: “Project for jobId X not accessible” } | There is a job for this jobDbId but the applicant can’t access it (for example because you try to access a job of another company) |
authorization error | 401 / 403 | See here and here for details. |
Example call with curl and user access token
1 |
curl -i -H "Authorization: Bearer 31cb2exx-001e-4b59-babc-f0815tdad47d" -H "Content-Type: application/json" -X GET "https://api.softgarden.io/api/rest/v3/frontend/jobs/4711/applied" |
Response:
1 |
true |
If yes, what is the ID of the application?
HTTP-Method
GET
Path
/api/rest/v3/frontend/jobs/{jobDbId}/application
Authetification
User Access Token
Path Parameter
jobDbId
Query Parameter
-none-
Responses
Action | Response | Description |
---|---|---|
success | ID of the application as string | |
error | 404 – JobPosting not fount 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 | 404 – { “code”: “get_project_error”, “message”: “Project for jobId X not available” } | There is no job for this jobDbId |
error | 404 – { “code”: “get_application_error”, “message”: “No application was found for job X” } | There is no application for this job and applicant |
authorization error | 401 / 403 | See here and here for details. |
Example call with curl and user access token
Successful request:
1 |
curl -i -H "Authorization: Bearer 31cb2exx-001e-4b59-babc-f0815tdad47d" -H "Content-Type: application/json" -X GET "https://api.softgarden.io/api/rest/v3/frontend/jobs/4711/application" |
Response:
1 |
76505as-99b5-45dgd-aaef-b59e5d4xxa46 |
Example call with curl and user access token
There is no application of that application on the job:
1 |
curl -i -H "Authorization: Bearer 31cb2exx-001e-4b59-babc-f0815tdad47d" -H "Content-Type: application/json" -X GET "https://api.softgarden.io/api/rest/v3/frontend/jobs/4712/application" |
Antwort:
1 2 3 4 |
{ "code": "get_application_error", "message":"No application was found for job 4712" } |