This content is still in draft.
seek-token
that your software received from the link out or Apply with SEEK flow.A seek-token
is supplied on a query string to your software in two ways:- When the candidate links out from SEEK to your apply form (see Step 1: Display button)
- After the candidate has authorized access to their profile (see Step 2: Handle authorization)
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 |
sendSignal
mutation, passing the seek-token
as the token
argument.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 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 sendSignal
exactly matches a seek-token
received with no additional encoding nor whitespace.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.