Skip to main content

SEEK

This integration controls posting to seek.com and its international partners like jobsdb.com and jobstreet.com.

Basic info​

Portal ID​

334

Enabling the posting provider​

Your clients will need to access the Connect your system page on their SEEK account and select idibu as their posting provider.

Login details​

Hirer ID (SEEK_rid)​

This will be provided by SEEK to the Client and must be an alphanumeric string, usually prepended with seekAnz:organization:seek:. Numeric Advertiser IDs have been deprecated and will not work.

Full Hirer ID, including seekAnz:organization:seek: can be provided in the field, but the final alphanumeric part alone will work as well.

Use Application Linkout (SEEK_linkout)​

If this optional field is set to N, the app_url Dynamic Core Field and the SEEK_url Extra Field will be ignored when posting to SEEK. Please see the section below for more context.

Application URLs & whitelabel partners​

Technically, idibu's SEEK integration does support Application URL Dynamic Core Field, as indicated by <extrafield name="SEEK_url" dynfield="app_url" description="Application URL" type="hidden" order="100"/> in the Portal's detailed information response.

However, SEEK does not allow external partners to redirect candidates to their application pages unless those pages are integrated with Apply with SEEK.

This limitation normally applies to all entities that satisfy the criteria of idibu's whitelabel or CRM partners.

The Apply with SEEK integration must be handled directly between your software (as you host and control the pages) and SEEK. Your idibu representative can help make introductions.

Until you are accepted as SEEK's partner and such an integration is completed, the only way to post jobs from your software via idibu to SEEK is by setting the SEEK_linkout Extra Field to N for each of your Client accounts, as part of SEEK's subscription settings - this way, idibu will not send your app_url (nor the SEEK_url Extra Field) to SEEK, even when provided. On top of that, the only way to gather SEEK candidates for such postings is through idibu's Applicant Management webservice.

Portal's detailed information requirements​

In order to correctly obtain all Extra Field data for SEEK, the following non-required parameters of the Portal's detailed information method are necessary:

  • location - required to generate the matching SEEK_loc list of options;
  • profileID - provide it if the posting User (or Office or Team to which that User belongs) has a specific SEEK_rid value;
  • title - not critical, but based on it, SEEK may return Category options that are most relevant to the job under the Recommended parent of the SEEK_sec field;

Also, please keep in mind that SEEK will not return any location data in the SEEK_loc field if an incorrect SEEK_rid value is assigned to the Client account (or the User profile identified by the profileID). As SEEK_loc is a mandatory Extra Field, it won't be possible to even attempt or test the posting without a functional SEEK_rid in the subscription settings.

Hidden Extra Fields​

There are three extrafield elements of type="hidden" returned in SEEK's Portal's detailed information:

  • SEEK_widget_enabled
  • SEEK_widget
  • SEEK_ques

These fields are internal idibu fields used for automated handling of SEEK-specific UI elements in the Post Completion Page. Please ignore and do not use these fields.

The other two hidden Extra Fields are standard Dynamic Core Fields:

  • SEEK_url
  • SEEK_osal

However, please keep in mind SEEK's Application URL limitations described above.