minimumAmount and maximumAmount are not visible in search results nor on the job ad.
The hirer can provide an optional salary description to describe the remuneration package,
and SEEK may display the pay type and currency alongside the description for clarity.The CommissionOnly value is now deprecated in RemunerationPackageInput.basisCode.
You should remove the option from your software.Monthly interval in certain markets.
This value is now supported in RemunerationRangeInput.intervalCode and complements the existing Hourly and Yearly intervals.{"basisCode": "Salaried",
"ranges": [
{
"intervalCode": "Month"
}
]
}payTypes query.
These may be presented to a hirer for selection in a job posting flow.This can help prevent entering a nonsensical pay type combination.
For example, a job ad with an hourly rate of $70,000 will render a hirer’s job ad undiscoverable in recommendations and searchquery ($schemeId: String!) {
payTypes(schemeId: $schemeId) {
basisCode
intervalCode
label
}
}NZD is required for positions located in New Zealand.
These are locations that have a countryCode of NZ.GBP is required for positions located in the UK & Ireland.
These are locations that have a countryCode of GB or IE.Note that this requires positions in the Republic of Ireland to use salaries denominated in GBP, even though their local currency is EUR.AUD is required for positions in all other locations, regardless of their local currency.currencies value returned for the hirer’s selected locationcurrencies query.
A query-based approach will allow your hirers to select new currencies if they are added in future.query ($usageTypeCode: String!) {
currencies(usageTypeCode: $usageTypeCode) {
code
}
}currencies for a given location.
The ISO 4217 currency codes are listed in order of preference.
In most cases there will be a single currency returned,
and we recommend pre-selecting the first option for an optimal hirer experience:{"contextualName": "Bukit Batok West Region SG",
"currencies": [
{
"code": "SGD"
}
],
"id": {
"value": "seekAnz:location:seek:2dE6LBwKu"
}
}USD.Previously, the SEEK API would silently ignore mismatched currency inputs and replace them with the expected currency for the position location.
For example, if you sent NZD for a job ad located in Australia, we would replace the currency with AUD.
This behaviour was erroneous as it did not account for currency conversions,
and it has been removed now that the SEEK API accepts any supported currency in any location.
The currency that your software provides will be respected on the job ad,
and providing an unsupported currency will fail with a BAD_USER_INPUT error.We have revised our UX recommendations for salary ranges.
These changes are focused on supporting Asia-Pacific markets and ensuring hirers get optimal performance from their SEEK job ads.