Jobs API - Predefined Location Identifier Support

Description

It is now possible to reference a predefined location by its identifier when creating or updating a job, instead of providing full location details.

This change is backward compatible. Existing clients sending location with city and countryCode continue to work without any modifications.

Jobs API

Added

• LocationByIdentifier schema — allows specifying a location using a company-configured predefined location identifier. Mutually exclusive with LocationDetails fields.
  • Required: identifier (string, 3–64 chars) — the unique identifier of a predefined location for the company.
  • Optional: remote, hybrid, hybridDescription — override the remote/hybrid settings from the predefined location.
• location.identifier accepted on POST /jobs and PUT /jobs/{jobId}.
• New error code LOCATION_IDENTIFIER_NOT_FOUND (HTTP 400) — returned when the provided identifier does not match any predefined location configured for the company.

Changed

• JobInput.location is now a oneOf of LocationDetails (city + countryCode) or LocationByIdentifier (identifier). Requests mixing fields from both schemas return HTTP 422.

References

• Jobs API