CandidateProfile
object links to:CandidateProfile.candidate
field.Candidate.person
contains the candidate’s name, home location, email address, and phone number.This field is connected to the candidate’s live SEEK Profile;
the query response will reflect updates made by the candidate after applying.Candidate.documentId
can be used as a stable identifier for the candidate across multiple applications.CandidateProfile.associatedPositionProfile
field.You can use this to associate the candidate application with a SEEK job ad and hirer.CandidateProfile.associatedPositionOpenings
field.You’ll likely be better off linking through the position profile;
this field is supported to align with HR-JSON.seekQuestionnaireSubmission
field.
This will only be present if a questionnaire was provided when posting the job ad.CandidateProfile
schema definition.
Only a name and email address are required to create a SEEK candidate account;
all other fields in a candidate’s profile are optional.SEEK may redact fields and omit PII when a candidate or application is deleted.
This includes attachments and questionnaire submissions.The SEEK API does not translate user input and will serve SEEK Profile information as supplied by the candidate.
As a result, your software may need to handle multilingual candidate data.Use the GraphQL candidateProfile
query to retrieve candidate profiles.
You should combine this with the query you use to retrieve attachments and questionnaire submissions.query ($id: String!) {
candidateProfile(id: $id) {
profileId {
value
}
createDateTime
candidate {
person {
name {
given
family
}
communication {
address {
# Select other address fields as necessary
formattedAddress
countryCode
}
phone {
formattedNumber
}
email {
address
}
}
}
}
associatedPositionProfile {
seekHirerJobReference
positionOrganizations {
id {
value
}
name
}
positionUri
}
employment {
organization {
name
}
positionHistories {
start
end
title
}
}
education {
institution {
name
}
educationDegrees {
name
degreeGrantedStatus
date
}
descriptions
}
certifications {
name
issued
effectiveTimePeriod {
validTo
}
issuingAuthority {
name
}
descriptions
}
qualifications {
competencyName
}
}
}