The SEEK API provides a number of fields that can be used to identify a position.
They fall into two separate categories:
- The
PositionOpening.documentIdandPositionProfile.profileIdfields are unique object identifiers assigned by the SEEK API.While these are the primary way to identify positions in the SEEK API, they’re not available on the SEEK employer website . - Reference fields are optional strings that can be provided when creating a position opening or posting a job ad. The SEEK API does not require that references are unique. Your software may reuse a reference across multiple job ads.Do not include any personal information such as a legal name or email address. Depending on the particular reference field, they can be used to correlate job ads posted via the SEEK API and the SEEK employer website.
The
PositionProfile.seekHirerJobReference field is a generic reference that can be set on a job ad and viewed across all channels.
This makes it useful for supporting cross-channel workflows such as exporting applications for jobs posted outside the SEEK API.
SEEK hirers typically use this as their primary reference due to its broad support.The
PositionProfile.seekBillingReference field is intended to contain a billing reference or cost centre code.
This field can be set on a job ad via the SEEK API, but is typically unavailable on the SEEK employer website.
It appears on hirer invoices & contract reporting from SEEK so that costs incurred can be attributed to the relevant business unit or department.The
PositionOpening.seekPartnerMetadata & PositionProfile.seekPartnerMetadata fields are intended to contain opaque metadata that’s useful to your software.
They can only be populated or retrieved via the SEEK API; they’re not directly exposed to SEEK hirers.Note that SEEK hirers can have relationships with multiple integration partners or move between integration partners over time.
The
PositionProfile.seekCreatedBySelfIndicator field can identify job ads posted by other integration partners so their metadata can be ignored.The table below shows which identifiers & references can be populated in each channel.
Field | SEEK API | SEEK employer website |
|---|---|---|
PositionOpening.documentId | ||
PositionOpening.seekPartnerMetadata | ||
PositionProfile.profileId | ||
PositionProfile.seekHirerJobReference | ||
PositionProfile.seekBillingReference | ||
PositionProfile.seekPartnerMetadata |
Referred to as “agent job reference”. Only available when posting as an agency on behalf of a hirer.
The table below shows which identifiers & references can be viewed in each channel.
Field | SEEK API | SEEK employer website | Hirer billing & reports |
|---|---|---|---|
PositionOpening.documentId | |||
PositionOpening.seekPartnerMetadata | |||
PositionProfile.profileId | |||
PositionProfile.seekHirerJobReference | Advertiser ad ID | ||
PositionProfile.seekBillingReference | Billing reference | ||
PositionProfile.seekPartnerMetadata |
Referred to as “agent job reference”. Only available when posting as an agency on behalf of a hirer.