Application complete signal
Application complete signal
The application complete signal signifies that a job application has been submitted in your recruitment software.
It applies to positions that are either advertised on SEEK or have the Apply with SEEK button enabled.
Note that it does not imply a candidate source or Apply with SEEK usage;
Ad Performance analytics will only attribute completed applications where the candidate source is SEEK.Once a candidate has completed and submitted your apply form,
your software must send an application complete signal to SEEK to signify form submission.
The application complete signal requires a 
You will receive the token in a 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 180 days from the time of generation.
If your software allows candidates to save a draft application, the token must be stored with the draft and used when the candidate submits the application.Should an expired token be provided to the
If you are implementing Apply with SEEK, refer to its documentation as your implementation of the application complete signal will differ from
the below.
seek-token that your software received from the link out flow.The application complete signal is only required if your software supports posting job ads that link out to an external apply form.seek-token parameter appended to the query string of the posted applicationUri.Text
Copy
https://example.com/position/123/apply?seek-token=eyJqb2JJZCI6MCwiY2FuZGlkYXRlSWQiOjAsInNlc3Npb25JZCI6IiJ9sendSignal mutation, the SEEK API will internally handle the error and no error message will be returned.When a candidate completes an application, the token must be stored with their application for potential future use.If a candidate returns to an apply form via the same SEEK link-out URL,
you will receive a new seek-token.
This should override any previous token for the job application when sending subsequent signals to SEEK.To send the application complete signal,
use the sendSignal mutation, passing the seek-token as the token argument.MutationVariablesResult
CopyGraphQL Explorer
mutation ($input: SendSignalInput!) {
sendSignal(input: $input)
}sendSignal will return errors consistent with our documented GraphQL error responses.
If your software receives authentication or transient server errors, it must retry sending of application complete signals as described in the documentation.We recommend that you log full requests and responses to the sendSignal mutation during development to facilitate debugging.
Use a unique X-Request-Id for each request to assist in support investigations.Below are common errors that may be returned when sending an application complete signal.
Refer to our GraphQL error responses for full details of errors returned from the SEEK API.extensions.code | message | Description | Resolution |
|---|---|---|---|
/input/token: Is not valid | The request has an /input/token that is not recognised. | Ensure the token sent in sendSignal exactly matches a seek-token received with no additional encoding nor whitespace. | |
Authorization header missing | The request does not have an Authorization header. | Ensure a partner token is passed in the Authorization header. | |
Live tokens are not accepted when accessing public test data | The request has a production Authorization header but its /input/token was taken from our documentation for Playground use. | Send real seek-tokens received from the link out flow. |