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.
Check with your SEEK contact before starting any build work described here.
This use case provides technical implementation details for the Apply with SEEK product.
More information can be found on the Apply with SEEK product page .
Apply with SEEK allows candidates to pre-fill an external apply form hosted by your recruitment software using information from their SEEK Profile.
Candidates can also attach their CV already stored on SEEK, making it easier to apply on desktop or mobile.
Apply with SEEK can be used where a candidate arrives on your hosted apply form via a SEEK job advertisement using link-out,
or where the candidate accesses the apply form in your software through another source.
In either case, the candidate can click the Apply with SEEK button to authorize access to their SEEK Profile,
and have their details pre-filled into the apply form.
The diagram below outlines the Apply with SEEK experience for a candidate starting on SEEK:
There are two sub-flows described here:
- Manual button flowThe candidate is first redirected to the external apply form. If they click the Apply with SEEK button on the form, they are then presented with the authorization page. Your software can pre-fill the form after this exchange.Previous versions of Apply with SEEK worked in this way, and it remains the default interaction model for now.
- Pre-authorization flowThe authorization page is presented to the candidate upfront, before they are redirected to the external apply form. Your software can pre-fill the form upon redirect.This streamlines the candidate’s experience when they start on SEEK, and is planned to be selectively enabled on more job ads over time.
Your software must support both flows as part of Apply with SEEK integration.
Before you start accessing the GraphQL queries for Apply with SEEK,
you will need to request a partner token.
To integrate the Apply with SEEK flow into your apply form, the following steps are required:
The diagram below shows an expanded sequence of a candidate applying via Apply with SEEK.
It details the interactions between your software and SEEK to pre-fill an apply form,
grouped by each step in the integration process.
The updated Apply with SEEK offers a user experience similar to its predecessor , while introducing several enhancements for both candidates and integration partners:
- It adopts a consistent approach with other SEEK API components, simplifying access and allowing you to apply the same API authorization and GraphQL methodologies used in other SEEK API integrations.
- The candidate’s authorization link is available via a GraphQL query, avoiding the need to hard-code auth link elements directly in your software.
- SEEK Profile information is retrieved using the same GraphQL
candidateProfilequery as our SEEK Optimised Apply service. - Introduces additional candidate fields that can be pre-populated into your apply form.
If you currently integrate with the previous version of Apply with SEEK , you will need to follow the same steps above to update your integration.
The table below outlines the key differences between the previous and current versions of Apply with SEEK:
Feature | Prior version (v1) | This version (v2) |
|---|---|---|
Legacy client credentials | SEEK API partner access tokens | |
No support | New seek-token passed in during link-out redirect | |
Link generated by partner | GraphQL applyWithSeekButton query returns link, branded image, and text localised for SEEK, Jobstreet, and Jobsdb | |
OAuth 2.0 with authorization code exchanged for access token | Revised authorization flow returning seek-prefill-id for retrieving SEEK Profile information and seek-token for application tracking | |
POST endpoint | GraphQL candidateProfile query | |
GET based on returned url | GET based on returned url | |
Partner pre-fills fields based on returned data | Partner pre-fills fields based on returned data | |
POST endpoint | GraphQL sendApplicationSignal mutation |