advertisementProducts
query,
which should be simpler to maintain over time and more flexible.Note the following high-level differences compared to the legacy ANZ-specific queries:positionProfile
input change.
For example, if the hirer selects a new location, you must re-render the panel to reflect updated products and pricing.When creating a job ad, your software must omit the optional profileId
field.
When updating a job ad, your software must provide its profileId
.limit
to the query so that SEEK can provide the most relevant set of products within your constraints.
Do not manually truncate the returned list as that may exclude highly relevant products.Classic
, StandOut
and Premium
.
Your software must not hardcode any logic based on specific ad product names or identifiers.
The names and identifiers of ad products may vary without warning, so hardcoding them could cause your integration to break and prevent hirers from posting job ads.AdvertisementProduct.features
supported by each product.Your software must conditionally display brand selection and search bullet point inputs based on these dynamic feature indicators.
You may have a similar capability if you integrated with the feature indicators of the previous Ad Selection queries,
but we now provide parameters that detail which brand components and how many bullet points are supported:{
"features": {
- "brandingIndicator": true,
+ "branding": {
+ "coverImageIndicator": false,
+ "logoIndicator": true
+ },
- "searchBulletPointsIndicator": true,
+ "searchBulletPoints": {
+ "limit": 3
+ }
},
// ...
};
AdvertisementProduct
object has a smaller selection of fields that can be directly mapped to your user interface.The ANZ-specific queries returned a price.visibleForHirerIndicator
field which your software had to read to determine whether to display the price.
Now, the new query internally handles price visibility.
Your software should display the products[].price.summary
if it is populated,
and hide the field if the price is null.selectedAdvertisementProductId
.
Ad selection will then pre-select an equivalent ad product and return new product IDs that can be used to post the job ad.Your software must omit the deprecated seekAnzAdvertisementType
field in favour of a seekAdvertisementProductId
sourced from our new panel or GraphQL query.
Your software should always omit unused arguments as a best practice to reduce the surface area of your integration.
Setting seekAnzAdvertisementType
will result in failed Job Posting create and update calls following the December 2024 retirement date.{
"postingInstructions": {
"seekAnzAdvertisementType": "Classic"
}
}
seekAnzAdvertisementType
field in favour of the new seekAdvertisementProduct
field.
Your software should only select the fields it uses as a best practice to reduce the surface area of your integration.
Selecting seekAnzAdvertisementType
will result in failed Job Posting queries following the December 2024 retirement date.# Inline arguments are only used to simplify these examples.
# Parameterise your production queries with variables.
# https://developer.seek.com/graphql/in-practice#variables
query {
positionProfile(id: "seekAnzPublicTest:positionProfile:jobAd:2782PZfXV") {
postingInstructions {
seekAnzAdvertisementType
}
}
}
seekAnzAdvertisementType
field in favour of a seekAdvertisementProductId
sourced from our new panel or GraphQL query.
Using seekAnzAdvertisementType
will result in failed Job Posting create and update calls following the December 2024 retirement date.Under certain circumstances,
it may be infeasible to present an ad selection interface to the hirer when an update is made.
For example, the update may be driven by a back-end process in your software rather than an individual user interacting with an update workflow.
In such scenarios, you should omit both seekAdvertisementProductId
and seekAnzAdvertisementType
to retain the current ad product.See the relevant use case documentation for more information.The following criteria need to be met before progressing to the next feature:Criteria | Description |
---|---|
Ad selection built | SEEK hirers can select available SEEK ad products and see pricing when creating or editing a job ad in your software |
Ad selection re-render implemented | SEEK hirers can see new products when the position location, job category or title has changed |
Ad selection fallback removed | SEEK hirers must not see a dropdown list of hardcoded ad types when the Ad Selection Panel fails to load |
User experience signed off | SEEK has signed off on your ad selection user experience |
Job ad posted successfully | Hirer can successfully post a job ad to SEEK with their selected ad product |
Job ad updated successfully | Hirer can successfully update a job ad to SEEK with their selected ad product |