Docs Job Posting Ad Sync Transition hirers

Transition hirers

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.

Directional If you have hirers using existing Ad Sync sources such as feed ingestion or web scraping, they can be migrated to Ad Sync via the SEEK API. This page outlines prospective approaches to gracefully migrate these hirers. Check with us before proceeding, as other approaches may be more appropriate to your situation.

Feed ingestion

Hirers can migrate from JSON or XML feed ingestion to the SEEK API.

1. Enable interoperability

Surface a unique identifier for each position in your software’s feed, and inform SEEK of the attribute or property path.When a job ad is posted to our employment marketplace, the SEEK API will emit a PositionProfilePosted event to partners with a Job Posting relationship with the hirer in question. Use this event to retrieve details of the job ad, which will include:

The unique identifier from your feed under seekHirerJobReference
A seekPostingSourceCode of AdSync
A seekCreatedBySelfIndicator of false

GraphQLVariablesResponse

CopyGraphQL Explorer

query ($id: String!) {

  positionProfile(id: $id) {

    seekHirerJobReference

    seekCreatedBySelfIndicator

    ... on PostedPositionProfile {

      seekPostingSourceCode

Use seekHirerJobReference to link the existing job ad to the appropriate position in your software, following our display guidance to ensure the hirer understands where the job ad came from.From here, your software can surface regular management features on the job ad, including the ability to edit it.

2. Backfill existing job ads

If your software was not already subscribed to the PositionProfilePosted event, you may backfill events for previously posted job ads to surface and manage them in flow.Follow our position sharing guidance and start synchronising positions via the SEEK API for the hirer in question.

4. Turn off the feed

Notify SEEK to disable ingestion of the XML or JSON feed.Job ads that were posted via feed ingestion will no longer receive updates. The hirer will be able to manually edit or close these job ads in your software via the interoperable flow described above, or on the SEEK Employer website.

Web scraping

Web scraping makes it challenging to consistently extract a unique position identifier needed for interoperability. Hirers migrating from web scraping will have more limited options to manage existing job ads.Follow our position sharing guidance and start synchronising positions via the SEEK API for the hirer in question.When a job ad is posted to our employment marketplace, the SEEK API will emit a PositionProfilePosted event to partners with a Job Posting relationship with the hirer in question. Use this event to retrieve details of the job ad.Use seekHirerJobReference to link the existing job ad to the appropriate position in your software, following our display guidance to ensure the hirer understands where the job ad came from.From here, your software can surface regular management features on the job ad, including the ability to edit it.

2. Turn off the feed

Notify SEEK to disable ingestion via web scraping.Job ads that were posted via web scraping will no longer receive updates. The hirer will be able to manually edit or close these job ads on the SEEK Employer website.

Ad Sync: Display job ads

Job Posting: Enhanced Job Posting