Job Posting - Developer FAQs

Note

This FAQ is meant for your development purposes only.

Questions Catalogue

- Product

  1. What are the different ways that a customer can post jobs on LinkedIn?
  2. How can I avoid Job Deduplication?
  3. Our customer cannot renew their closed job via Premium Job Posting. How can I do that?
  4. Our customer is having issues with their HTML formatting not getting honored in the job description. Why is this happening?
  5. Why is my customer unable to post jobs on LinkedIn for specific locations?
  6. What are the reasons a Basic Job doesn’t appear on LinkedIn?
  7. Many of our customer jobs are getting posted to LinkedIn via XML feed and Job Wrapping. What happens when the same jobs get posted via Premium Job Posting?
  8. Can a job posted via the Job Posting API replace old or backfilled jobs in the Recruiter dashboard?
  9. How do I know if the location provided will be standardized correctly?
  10. Are alternate location postings supported by all type of PJP contracts such as job posts, job slots? Are customers charged differently?
  11. When a candidate applies to a posting with alternate locations, is the location of origin communicated back to the ATS?
  12. Is there any difference in terms of performance between a single free/premium posting with three alternate locations, versus three individual free/premium postings with a single location?

- Integration

  1. How can my customers enable a Premium Job Posting Partner in their Recruiter Account?
  2. How can we get contract and company details of a customer? Is there a way for LinkedIn to provide this information?
  3. Job Location of our customer is not getting accepted by the Premium Job Posting. How can I ensure their job location is valid?
  4. Our customer job was posted successfully but it cannot be viewed. What went wrong?
  5. How can our customers post Remote Jobs via Premium Job Posting?
  6. Can customers enable a tracking pixel with Premium Job Posting?
  7. Is there any throttling limit to the number of promoted jobs that can be posted?
  8. Is there any URL or Query String length limit that integration partner needs to comply with?
  9. Provisioned Applications response is not recorded due to some error, how can we obtain client secret?
  10. How to update validJsSdkDomains in the customer application?
  11. If the widget callback fails in partner ATS, how can we get the customer contract id?

- Support

  1. What can I do in a scenario where we cannot fix locations and other fields for jobs created via API?
  2. How can we fix default job poster related issues?
  3. How can I help customers when their Job Slots are full?
  4. How can I surface feedback on the Premium Job Posting to LinkedIn?
  5. How can I allocate Job Slots between Recruiters?
  6. Can I completely disable manual job posting into job slots from LinkedIn Recruiter dashboard and allow ATS to manage it?
  7. What would happen if we remove the default job poster?

Questions and Answers

Product

What are the different ways that a customer can post jobs on LinkedIn?

Please reference Job Posting documentation

How can I avoid Job Deduplication?

  • If a customer is using Job Wrapping and Premium Job Posting API, there could be a risk that these jobs are duplicated.
  • Between Basic and promoted jobs, our system prioritizes jobs that are promoted.
  • It is recommended that customer uses either API or XML Feed based jobs to avoid duplication

Our customer cannot renew their closed job via Premium Job Posting. How can I do that?

You can RENEW only an open job. If the Job is CLOSED, a new request for the job needs to be sent with jobPostingOperationType: CREATE

Our customer is having issues with their HTML formatting not getting honored in the job description. Why is this happening?

This is dependent on the HTML tags being provided. To know what HTML tags are supported please refer to these API documentation

Why is my customer unable to post jobs on LinkedIn for specific locations?

Please refer to the following help center article

What are the reasons a Basic Job doesn’t appear on LinkedIn?

In some cases, we may require certain types of jobs to be promoted on LinkedIn. Jobs that require promotion may include jobs by companies with generic names (such as “Confidential Company”) or jobs from search and staffing companies. These limits are designed to prevent abuse, improve product quality, and increase transparency while ensuring that job seekers have access to the best possible opportunities. Please note that LinkedIn reserves the right to require promotion of jobs.

Many of our customer jobs are getting posted to LinkedIn via XML feed and Job Wrapping. What happens when the same jobs get posted via Premium Job Posting?

It depends on the integration.

  • For the partners who have integrated with LinkedIn's Apply Connect program, the promoted jobs posted via /simpleJobPosting API will close out existing scraped and wrapped jobs
  • For the remaining partners, whichever job was posted first will stay up. If a job is posted via Job Wrapping first, the Simple Job Posting (SJP) job does not post if it has the same unique partner identifier. In such cases, the task status response outlines the following error message:
    • "Trying to create a job with the same partnerIdentifier already exists! Dropping the duplicate job posting creation request. JobId: 123456789, partnerIdentifier: {partner=urn:li:jobPostingPartner:{id}, partnerJobCode=Test123456}."

Can a job posted via the Job Posting API replace old or backfilled jobs in the Recruiter dashboard?

No, if you have used your job slots you will receive an error message indicating that there are none remaining. You are unable to replace to backfill jobs

How do I know if the location provided will be standardized correctly?

Answer: We do not have a utility tool or an API that can help validate a location match. However, refer to the Help Article for few guidelines to ensure improved accuracy for location matching.

Are alternate location postings supported by all type of PJP contracts such as job posts, job slots? Are customers charged differently?

Yes, they are supported by all types of PJP contracts, and each multiplexed job takes up an additional slot for job slots. For FP4P, customer will need to set separate budgets for each job.

When a candidate applies to a posting with alternate locations, is the location of origin communicated back to the ATS?

For jobs with alternateLocations, we will mirror career site experience and provide application back to original jobpostingID. If customer is trying to tie applicants to specific cities, customer should include a question in application flow to capture preferred location.

Is there any difference in terms of performance between a single free/premium posting with three alternate locations, versus three individual free/premium postings with a single location?

There should not be a performance difference.

Integration

How can my customers enable a Premium Job Posting Partner in their Recruiter Account?

Please refer to this Help Article

How can we get contract and company details of a customer ? Is there a way for LinkedIn to provide this information?

  • A customer needs to manually provide these details and the partner ATS should provide support to take both LinkedIn Contract ID and Company ID as input.
  • Dependent on ATS / Job Distributor this may be done through the UI or manually through support teams
  • Below Help Article links can be shared to help customers find their Contract and Company ID:

Job Location of our customer is not getting accepted by the Premium Job Posting. How can I ensure their job location is valid?

Ensuring the right format of the location details are outlined here

Our customer job was posted successfully but it cannot be viewed. What went wrong?

  • In order to troubleshoot this issue please collect the following information from the customer:
    • Request Headers, Request Body, Response Headers & Response Body to be shared for both Job Posting and Job Task Status API
    • Submit ticket to GCO support
  • Few scenarios why this may happen are:
    • Job got marked as Spam
    • Job Poster User is marked as Spam

How can our customers post Remote Jobs via Premium Job Posting?

Customers can achieve this by setting the ‘workplaceTypes’ field as remote. For more details refer to Job Posting API Schema

Can customers enable a tracking pixel with Premium Job Posting?

Yes, please refer to the following help center article

Is there any throttling limit to the number of promoted jobs that can be posted?

Yes, please refer to the following API documentation

Is there any URL or Query String length limit, that integration partner needs to comply with ??

Yes, please refer to the following API documentation

Provisioned Applications response is not recorded due to some error, how can we obtain client secret?

In this case, you need to check if the application is created or not using uniqueForeignId, if the application is not created you can request it again with the same uniqueForeignId otherwise you need to create a new application with a new uniqueForeignId.

How to update `validJsSdkDomains` in the customer application?

Provisioning APIs allow partners to update customer applications, This will override the existing list of JavaScript SDK domain names with the list of domains in the request body of this POST call.

If the widget callback fails in partner ATS, how can we get the customer contract id?

You can ask customers to opt in again with the widget. Unless "update customer integration" call goes through API job postings will not be active for customers.

Support

What can I do in a scenario where we cannot fix locations and other fields for jobs created via API?

  • If you are able to post to LinkedIn and can find the location on Bing Geo, you should be able to post via the API
  • If there is a valid location not mapping properly, we can map it to post if it is valid. Please reach out to LinkedIn Customer Support ltsatsintegrations@linkedin.com for the same
  • We cannot create custom mapping; the client must supply the right location info/string
  • In such cases, the task status response outlines this error message: "Caller is not authorized to access the jobs for contract: urn:li:contract:189990
  • Troubleshooting steps will be
    • Ensure Customer has configured Job Poster correctly. Refer to Help Article
    • Ensure poster email is the primary email on LinkedIn profile and seat holder on the above contract
    • Admin should check if the default poster is a valid seat holder (sometimes this is not updated if someone is removed from the Recruiter dashboard)

How can I help customers when their Job Slots are full?

  • This issue may arise when customers are manually posting jobs in Recruiter or using Job Wrapping while also using a Job Posting Partner
  • An admin can check job slot availability within the Recruiter dashboard product settings
  • Please refer to the following help center article

How can I surface feedback on the Premium Job Posting to LinkedIn?

If the Partner has questions on the integration, please ask them to reach out to Zendesk partner support platform and copy to their LinkedIn Business Development and Partner Engineering point of contact directly.

How can I allocate Job Slots between Recruiters?

As an admin, you can determine how job slots are allocated across your recruiting team. Click here to learn more about managing job slots and the ability to disable manual job posting for users.

Can I completely disable manual job posting into job slots from LinkedIn Recruiter dashboard and allow ATS to manage it?

Yes, this is possible. Ensure that your ATS is integrated with LinkedIn’s Premium Job Posting program and then follow the steps mentioned in the article here. To disable the functionality, select the Do not allow manual job postings option.

What would happen if we remove the default job poster?

If the default job poster is removed from the contract after widget integration, Job postings via API will fail until you go through the widget opt-in process to select a new default job poster again.