Step 6: Send 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 seek-token that your software received from the link out or Apply with SEEK flow.

Handling multiple seek-tokens

A seek-token is supplied on a query string to your software in two ways:
  1. When the candidate links out from SEEK to your apply form (see Step 1: Display button)
  2. 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 from the Apply with SEEK authorization flow.
Candidate source
Using Apply with SEEK
Send signals
Token handling
SEEK
Use new seek-token from the Authorization flow step to send signals
SEEK
Use original seek-token from linking out to send signals
Other source
Use new seek-token from the Authorization flow step to send signals
Other source
No seek-token will have been received by your software, do not send signals

Sending the application complete signal

To send the application complete signal, use the sendApplicationSignal mutation, passing the seek-token as the token argument.
MutationVariables
CopyGraphQL Explorer
mutation ($input: SendApplicationSignalInput!) {
  sendApplicationSignal(input: $input)
}

Troubleshooting

sendApplicationSignal will return errors consistent with our documented GraphQL error responses. If your software receives authentication or transient server errors, it should retry sending of application complete signals as described in the documentation.A BAD_USER_INPUT error may occur if there is a structural issue with the token. Ensure the token being sent in sendApplicationSignal exactly matches a seek-token received with no additional encoding nor whitespace.We recommend that you log full requests and responses to the sendApplicationSignal mutation during development to facilitate debugging. Use a unique X-Request-Id for each request to assist in support investigations.
Apply with SEEK: 5. Populate form
Use cases: Ad Performance