Unposted positions allow your software to share information about positions that are currently being hired for.
All positions being actively recruited for should be shared with Talent Search.
When a hirer purchases a profile in Talent Search they will be prompted to select an unposted position to associate the purchase with.
Changes to positions within your software should be reflected in the SEEK API within 60 seconds .
PositionOpenings are the SEEK API’s representation of a job requisition.
A given opening may be shared between Job Posting and Proactive Sourcing use cases.See the position opening documentation for further context and supported operations.
An
UnpostedPositionProfile represents the details of an open position not posted to the SEEK job board.
They share most of their structure with the PostedPositionProfile used to represent a posted job ad.
However, they lack the PostingInstruction object used to facilitate the posting process.The
createUnpostedPositionProfileForOpening mutation creates an unposted position profile under an existing position opening.MutationVariablesResult
Copy GraphQL Explorer
mutation ($input: CreateUnpostedPositionProfileForOpeningInput!) {
createUnpostedPositionProfileForOpening(input: $input) {
positionProfile {
profileId {
value
}
}
}
}profileName is an optional free-text input field that is rendered alongside the positionTitle to help disambiguate the profile.
This is useful for agencies that may hire similar positions on behalf of multiple hirers.
For example, if you supply the name of the position’s company, the end user will see a Talent Search combobox along the lines of:Customer Mobility Director (Melbourne)
Reference #, Acme Corp, Gabriella H
Customer Mobility Director (Auckland)
Reference #, Contoso, Lucy F
Assistant to the Product Director (Perth)
Reference #, Vandelay Industries, Gemma B
You can hover your mouse over the above example to view the corresponding input fields.
The
updateUnpostedPositionProfile mutation updates an existing unposted position profile.The position profile’s existing fields will be replaced with the provided input fields.
You must provide the current values of any fields you don’t want to modify.
MutationVariablesResult
Copy GraphQL Explorer
mutation ($input: UpdateUnpostedPositionProfileInput!) {
updateUnpostedPositionProfile(input: $input) {
positionProfile {
profileId {
value
}
}
}
}The
deleteUnpostedPositionProfile mutation deletes an unposted position profile and removes the unposted position from Talent Search.
Your software should use this mutation when the corresponding position is no longer being hired for.This will not remove information that has been associated with the position profile,
such as placement information within a candidate’s interaction history.
This operation should be avoided once other objects reference the position profile.
MutationVariablesResult
Copy GraphQL Explorer
mutation ($input: DeleteUnpostedPositionProfileInput!) {
deleteUnpostedPositionProfile(input: $input) {
positionProfile {
profileId {
value
}
}
}
}