Jobs API - Predefined Location Identifier Support in Job PATCH and Job Ads

Description

It is now possible to reference a predefined location by its identifier when updating a job via PATCH, and when creating or updating a job ad, consistent with the existing support in Create and Update Job.

This change is backward compatible. Existing clients sending location with full location details (city, countryCode, etc.) continue to work without any modifications.

Jobs API

Added

• location.identifier accepted on PATCH /jobs/{jobId}, using the same LocationByIdentifier schema already supported on POST /jobs and PUT /jobs/{jobId}.
• LOCATION_IDENTIFIER_NOT_FOUND (HTTP 400) is now also returned from PATCH /jobs/{jobId} when the provided identifier does not match any predefined location configured for the company.

Job Ads API

Added

• location.identifier accepted on POST /jobs/{jobId}/jobads and PUT /jobs/{jobId}/jobads/{jobAdId}.
• LOCATION_IDENTIFIER_NOT_FOUND (HTTP 400) returned from both endpoints when the provided identifier does not match any predefined location configured for the company.

References

• Update a job
• Create a new job ad
• Update a job ad