ApplicationExport
relationship with the SEEK hirer before posting a job ad that uses SEEK’s Apply Form.SEEK’s Apply Form is used when no additional applicationMethods
are provided in PostingInstruction
:{
// Default to SEEK’s Apply Form
"applicationMethods": null
// Other posting instruction fields
}
ApplicationUri
capability.
You can also use the hiringOrganization
query or self
query to achieve the same effect:query ($id: String!) {
hiringOrganization(id: $id) {
seekApiCapabilities {
applicationMethodCodes
}
}
}
applicationUri
on the job ad’s ApplicationMethodInput
.
This replaces SEEK’s Apply Form with an external apply form,
so Optimised Apply and questionnaires are not available.A link-out PostingInstruction
looks something like this:{
// Set explicitly to an external apply form
"applicationMethods": [
{
"applicationUri": {
"url": "https://example.com/position/123/apply"
}
}
]
// Other posting instruction fields
}
{
"errors": [
{
"message": "Invalid application URL: Application linkout not permitted",
"extensions": {
"code": "BAD_USER_INPUT",
"invalidFields": {
"/input/positionProfile/postingInstructions/0/applicationMethods/0/applicationUri/url": "Application linkout not permitted"
}
}
}
],
"data": null
}
applicationUri
.
This avoids the maintenance burden of strict URL allowlists.Follow best practices around URL redirection to protect candidates from phishing attempts.
At a minimum,
your software must have server-side provisions to ensure the applicationUri
points to a web resource that your organization manages,
and prevent bad actors from manipulating redirection behaviour.See the OWASP cheat sheet for best practices,
and our Terms of Use for more information about your obligations.