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.
Once the candidate has completed and submitted your apply form,
your software must send a Completion Signal to SEEK to indicate that the application process is complete.
The Completion Signal requires a
seek-token
token your software will have received during the Apply with SEEK flow.A
seek-token
is supplied on a query string to your software in two ways:- When the candidate initially 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
seek-token
received during the candidate authorizes access.Candidate Source | Using Apply with SEEK | Token handling |
---|---|---|
SEEK | seek-token returned during the Authorization flow step should be used for the Completion Signal | |
SEEK | As no authorization occurred, the original seek-token received when the candidate arrived from SEEK should be used for the Completion Signal | |
Other source | seek-token returned during the Authorization flow step should be used for the Completion Signal | |
Other source | No seek-token will have been received by your software, do not submit a Completion Signal |
To send the Completion Signal, use the
sendApplicationSignal
mutation , passing the seek-token
as the token
argument .