Introduction

The SEEK API provides access to SEEK’s employment marketplace. This documentation is targeted at developers integrating their recruitment software with SEEK.

Use cases

The SEEK API provides a unified way to access a shared set of HR-related objects. While there is a single SEEK API, there are a number of ways to use the API to accomplish specific goals:
As the SEEK API gains more functionality it will add new objects and fields to its existing schema. This lets you leverage your existing development effort and knowledge to access future SEEK features.

Integration process

SEEK uses a seven stage process for developing integrations with the SEEK API to ensure a high quality experience for our mutual hirers:
  1. Review the documentation
    Read through the documentation available on this website, and the SEEK API Terms of Use , to understand the concepts of the SEEK API and the scope of integrating it with your software.
  2. Request to integrate
    Fill in our integration request form , or reach out to your dedicated Partner Manager, to get started. We’ll be in contact to guide you through the process and set up your access to the Developer Dashboard .
  3. Build and test with the Playground
    Once you can access the Developer Dashboard, provision Playground credentials on the Developer Dashboard’s credentials page . These credentials grant you limited permissions to the SEEK API’s read-only mock data; use them to test accessing the SEEK API and mapping its data structures. While you can test the input validation of mutations with these credentials, the SEEK API will ultimately forbid requests to mutate our read-only mock data.
    The Developer Dashboard also provides a view of your live hirer relationships and events. This will give you visibility on your production SEEK API access before requesting your partner credentials.
  4. Request live credentials
    Once you’ve reached the limits of what you can do with the Playground, contact SEEK to request access to manage live partner credentials.
    Once approved, provision your live credentials using the Developer Dashboard’s credentials page . Live credentials grant you access to live production data.
    At the same time, SEEK will add a relationship between your partner account and an unsearchable SEEK test hirer. Test hirers can export candidate applications and post job ads free of charge, but their job ads don’t appear in SEEK’s search results. This should be sufficient to test your software end-to-end against the SEEK API.
  5. Test your integration
    SEEK may share a test plan with you to ensure your integration meets our quality standards. In addition, we may require access to your sandbox/test environment as applicable, to do our own validation. This is an important milestone for your integration, ensuring it meets user experience expectations and appropriately represents SEEK’s value proposition.
  6. Release your integration
    When you’re ready to go live, contact SEEK to discuss your release plans. For initial integrations, SEEK will work with you to ensure a smooth transition for you and our mutual hirers. In some cases, this may involve a limited pilot release to a subset of your customers.
    For ongoing changes to your integration, SEEK asks to remain informed of your release plans. This allows us to communicate accurate information to our mutual hirers during Sales and Support interactions.
  7. Maintain your integration
    Subscribe to our release notes to stay informed of changes as they reach general availability and evolve your integration accordingly.
    Review our Monitoring documentation to understand how to monitor your integration’s performance and troubleshoot issues, including use of the Developer Dashboard . Contact SEEK’s support team  for ongoing technical support.
We recommend to repeat these steps for any new development, not just for your initial integration. In particular, continue to use your Playground credentials for exploratory testing, as your partner credentials are highly sensitive.

Technology

The SEEK API leverages existing industry standards whenever possible. The core of the API is built on:
  • OAuth 2.0  for authenticating our integration partners to SEEK.
  • GraphQL for exposing our graph of positions , candidates  and other business objects.
    GraphQL allows you to query and join SEEK’s objects together in whatever way best suits your software. It also gives SEEK insight into how its API is being used and which fields our partners are interested in.
  • HR Open standards  as the basis of our GraphQL schema.
    Your software may already be using an existing HR Open standard such as HR-XML or HR-JSON. HR Open provides us with common, neutral terminology for concepts in the recruitment software space.
  • Webhooks to inform our partners of events that occur on SEEK.
  • Web-based components to ease feature adoption.
    SEEK provides embeddable and hosted experiences that save you the time of building every use case feature from scratch. These components comply with web standards and are implemented in HTML, CSS and JavaScript.

Multi-market support

While the SEEK API was initially launched in Australia & New Zealand (ANZ), it was built to be extended to other markets within the SEEK Group .
The SEEK API is now enabled across our Asia-Pacific (APAC) markets:
Code
Name
Brand
HK
Hong Kong
ID
Indonesia
MY
Malaysia
Jobstreet
PH
The Philippines
Jobstreet
SG
Singapore
Jobstreet
TH
Thailand
Jobsdb
Our documentation has been revised with guidance on regional features for new integrations.
If you previously built an integration for the Australia & New Zealand markets, refer to the 2023 Job Posting revision to accommodate changes to the SEEK marketplace as we have expanded across the Asia Pacific.