Skip to content

Applicants

List of valid attributes:

AttributeDescriptionSpecifics
application_stage_idID of the application stage the applicant belongs toCannot be set
created_atTimestamp when the applicant was createdCannot be set
emailEmail address of the applicantMust be set
nameName of the applicantMust be set

The following relationships can be included in requests:

RelationshipType
job_postingbelongs_to

List

Example response:

{
"data": [
{
"id": "1e9f83a6-51a7-445a-bd6e-5e0350f24c93",
"type": "applicant",
"attributes": {
"application_stage_id": "459e0b1e-caa0-4960-be61-dad0dbcd969e",
"created_at": "2023-10-15T10:30:00Z",
"email": "[email protected]",
"name": "John Doe"
}
}
// ...
]
}

This endpoint returns all applicants for the current account.

HTTP Request

GET /api/v1/applicants

Create applicant (public endpoint)

Example request:

{
"data": {
"type": "applicant",
"attributes": {
"name": "John Doe",
"email": "[email protected]",
"job_posting_id": "1e9f83a6-51a7-445a-bd6e-5e0350f24c93"
}
}
}

Example response:

{
"data": {
"id": "1e9f83a6-51a7-445a-bd6e-5e0350f24c93",
"type": "applicant",
"meta": {}
}
}

This endpoint creates an applicant for a published job posting. The applicant will be automatically assigned to the first application stage of the job posting’s account.

HTTP Request

POST /public/v1/applicants

Request Parameters

ParameterDescriptionRequired
nameFull name of the applicantYes
emailEmail address of the applicantYes
job_posting_idThe id of the job posting to apply toYes

Notes

  • The job posting must be active
  • Each email can only apply once per job posting
  • The applicant will be assigned to the first application stage automatically
  • If any validation fails, an empty 422 response will be returned