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.
If you are implementing Apply with SEEK, please refer to the Apply with SEEK documentation, as your implementation of Completion Signals will vary from the below.
The Completion Signal is a message sent to SEEK to notify that an application has been completed within your recruitment software.
When a candidate chooses to apply to a link-out job advertised on SEEK, they will be redirected to your application form along with a unique token.
This token should be passed back to the SEEK API once the candidate successfully submits their application.
Please note, the Completion Signal is only required if you are posting job ads that link out to an application form hosted by your recruitment software.
You will receive the token in a
seek-token
parameter appended to the query string of the posted applicationUri
.Text
Copy
https://www.example.com/job/123445/?seek-token=93WyyF1h6eaeb58ccc384b0e8353daa3011f1ece
The token is unique to that specific candidate, job ad and session, and should be stored for the duration of the application process.
Tokens remain valid for 30 days from the time of generation, and can be stored while a candidate drafts their application.
Tokens do not need to be stored for more than 30 days.
Should an expired token be provided to the
sendApplicationSignal
mutation, the SEEK API will internally handle the error and no error message will be returned.If a candidate returns to an application form via the same SEEK link-out URL, the new token generated should be returned to SEEK in the Completion Signal, and any previous token discarded.
When the application is completed, the token can be passed back via the
sendApplicationSignal
mutation .