Job Posting Announcements and Release Notes

Documented duplicate job error (ErrorCode:2009)

  • Documented the downstream-wrapped duplicate-job error (ErrorCode:2009) in the Check Job Operation Task Status error codes table, including a sample FAILED response and a note that it is an alternate surface of the existing duplicate-job failure.

Task URN multiplexing for multi-location jobs

Application secret management APIs

  • New Child Application Secret Management APIs - Added support for rotating and deleting secrets for parent, child, and standalone applications. Partners can now maintain up to two active secrets per application, enabling zero-downtime credential updates. See Application Secret Management for implementation details.

Job poster email requirement and posting guidelines

  • Job Posting guidelines: New guidelines are added to require a valid email address associated with the job posting owner (see the last bullet in point 2.) and restrict access to LinkedIn integration to paying users (see point 7.) in Third-Party Job Listing and Job Site Inclusion Guidelines.
  • XML feed: The XML feed schema is updated to require inclusion of the job poster email for each job.
  • Job Posting API: The Unversioned API and Versioned Job Posting API schema are updated to require inclusion of the job poster email for each job.

LinkedIn Apply free application limit error code

  • A new error code 1157 is added to indicate when LinkedIn Apply is disabled due to exceeding the free application limit. To restore LinkedIn Apply, promote the job to a paid job slot. To learn more, see LinkedInApplyStatus Error Codes.

Versioned API release cycle and schema changes

  • LinkedIn's Talent APIs are transitioning to a versioned API release cycle starting with the January 2025 release under a new base path: https://api.linkedin.com/rest/, see LTS API Documentation Versioning. As of January version release, only Simple Job Posting API supports versioning. You can leverage latest schema by calling the API with header 202501.
  • Recruiter Extension Schema is no longer supported in versioned simpleJobPosting API. For RSC partners a new Requisition API will be soon released in April 2025 to manage private jobs aka application tracking system job requisitions for 1-Click Export.
Endpoint Field Change(s) Required
/simpleJobPostings jobPostingOperationType Two more operation types are added to the enum i.e. UPGRADE, DOWNGRADE. UPGRADE: promote a free job to paid; DOWNGRADE: de-promote a paid job to free.
/simpleJobPostings expireAt Default expiry date is set to 180 days for all types of jobs. Max expiry date is relaxed to 365 days.
/simpleJobPostings availability Every job must be either PUBLIC or INTERNAL. We have removed PRIVATE_TO_ATS_INTEGRATION. You can map the requisition to a PUBLIC job using partnerRequisitionId. We are soon launching a requisition API for RSC partner's to provide more flexibility around jobs and requisition mapping.
/simpleJobPostings company Company URN of this job, previously referred via integrationContext field. You can use the company lookup API to fetch company details.
/simpleJobPostings integrationContext This field is deprecated and can be replaced by company,companyName or companyPageUrl
/simpleJobPostings partnerRequisitionId The Unique ID of the job requisition, which links the job posting to ATS requisition. All job posting customers can use this field to map ATS job requisition to LinkedIn jobs. This field is required for RSC customers using RSC integration.

Company and location lookup APIs

  • Introduced a new optional module featuring helper APIs for searching Company IDs and Locations.
  • These APIs are versioned and will remain optional for now. For details, see Company & Location Lookup API.

Certification test case restructure

Inline upgrade and downgrade for API jobs

  • Inline upgrade and downgrade for API Jobs

    • Inline upgrades from Basic API Jobs to Premium Jobs and downgrades from Premium API Jobs to Basic Jobs are now available.
    • The updated guidelines are available here.

  • XML Feed

  • Job Posting API

    • A new legal requirement has been added to indicate new limits for third-party jobs that are ingested as Basic Jobs
    • Added new FAQ questions to Developer FAQs

Multi-location job task status schema update

  • SimpleJobPostingTask Schema
    • Add location field to response for jobs that use alternateLocations or have customer defined multiple location job rules.
    • Starting June 30, 2024, we will no longer support countryCode, postalCode, workRemoteAllowed, and state schema field. Please use location instead of countryCode and postalCode. workplaceTypes instead of workRemoteAllowed. Do not send the state field as it will be automatically determined by LinkedIn, based on the jobPostingOperationType.

Premium job expiration and schema field updates

  • Premium job postings will now honor schema with expireAt field along with the basic job postings. The expiration date must be within the range of 1 to 90 days. For invalid date, API returns an "Invalid ExpirationDate" error.
  • Updated Job Posting Status API and Job Posting Status Notifications schema with expireAt field.
  • Updates to alternateLocations and workplaceTypes schema fields in XML Feed and Job Posting API schema

Create Jobs API error details update

Product FAQ additions

  • Added new FAQ questions to Product FAQs

FAQ, task ID lifespan, and schema field updates

Customer configuration widget updates

Removed companyDescription field

Company page URL, Basic Jobs naming, and task status updates

  • Job Posting API Schema
    • Added new field companyPageUrl to support better job to company mappings.
    • Updated requirements of fields: employmentStatus, experienceLevel, categories, workplaceTypes, description, location. companyJobCode, companyName, companyPageUrl, posterEmail.
  • Updated Limited Listings naming convenion to Basic Jobs

The following updates are made to Check Job Operation Task Status

  • Lifespan for task IDs is increased to 30 days
  • New status values PROCESSED added

Industry codes update for XML feeds

Premium job onboarding widget and field definitions

  • Added new customer onboarding widget for premium jobs. You can embed this widget in your platform to allow customers to log in and choose the premium job posting contract and enable premium job posting from the partner platform
  • Updated field definitions for industries and categories field

TYPEAHEAD enum removal

XML feed indexation frequency increase to 6 hours

  • XML feed indexation for ATSs is increased from 12 hrs to every 6 hrs

XML feed indexation, workplace types, and remote field sunset

  • XML feed indexation for ATSs has been increased from 24 hrs to every 12 hrs
  • Introduced workplaceTypes field in job posting schema to mark workplace nature of jobs. This field will be available for use by January 4, 2022
  • IsRemote field to be sunset from November 1, 2022
  • Added customer facing FAQ section to Developer FAQs

Workplace types and schema deprecation for API

  • Introduced workplaceTypes field in job posting schema to mark workplace nature of jobs. This field will be available for use by January 4, 2022

  • Revised description to include recommended value formats for location field

  • All partners need to adopt the latest Job Posting API's Schema by November 1, 2022. This means all partners should stop using fields mentioned in table below and marked with '*' in the schema

A consolidated summary of the changes that the API partner needs to take care of is given below:

Job Posting API changes

Endpoint Field Change(s) Required
/simpleJobPostings postalCode postalCode field will be deprecated. We recommend using the location field instead
/simpleJobPostings countryCode countryCode field will be deprecated. We recommend using the location field instead
/simpleJobPostings workRemoteAllowed workRemoteAllowed field will be deprecated. We recommend using the workplaceTypes field instead. This field will be available for use by November 15, 2022
/simpleJobPostings state state field will be deprecated. We recommend using the jobPostingOperationType field instead. Thus, the state.listed field should be replaced by jobPostingOperationType.create and state.closed field should be replaced by jobPostingOperationType.close field
/simpleJobPostings expireAt A value greater than 180 will not be allowed for the expireAt field. ATS should display to customers that the life of the job posting on LinkedIn will be 180 days and reflect the status as CLOSED on LinkedIn after 180 days. Once the job posting is closed on LinkedIn, it will be good to provide customers the support to RENEW the job posting or configure Auto-Renew in which case, ATS/Partner can renew the jobs proactively after 180 days if the job posting is still in LIVE/OPEN state on partner platform

Unified Job Posting API and certification

Basic Jobs XML feed launch

  • Basic Jobs Release of Basic Jobs XML feed format and FAQ.
  • Last updated on