This content provides an early look at an upcoming extension to the SEEK API. You may use it to scope integration effort, but the features described are not fully implemented and may be adjusted ahead of a production release.
Please check with your SEEK contact before starting any build work described here.
After the candidate has filled out the application form and submitted it, your software must send a Completion Signal to SEEK to indicate that the application process is complete.
The Completion Signal requires a
seekid token your software will have received during the Apply with SEEK flow.A
seekid is supplied on a query string to your software in two ways:- When the candidate initiailly arrives at your site from SEEK (see Step 1. Display button)
- After the candidate has authorized access to their profile (see Step 2. Handle authorization)
If your software has received both, it should retain only the second
seekid received during the candidate authorizes access.Candidate Source | Using Apply with SEEK | seekid handling |
|---|---|---|
SEEK | seekid returned during the Authorization flow step should be used for the Completion Signal | |
SEEK | As no authorization occurred, the original seekid received when the candidate arrived from SEEK should be used for the Completion Signal | |
Other source | seekid returned during the Authorization flow step should be used for the Completion Signal | |
Other source | No seekid will have been received by your software, do not submit a Completion Signal |
To send the Completion Signal, use the
_unstable_sendApplicationSignal mutation, passing the seekid as the token value.MutationVariables
CopyGraphQL Explorer
mutation ($input: _unstable_sendApplicationSignalInput!) {
_unstable_sendApplicationSignal(input: $input)
}