Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
As a partner, you can integrate with Apply Connect using the Job Posting API. This API helps you create and manage Apply Connect jobs on LinkedIn for your customers. LinkedIn members can view these job postings and apply to them directly on the platform. Additionally, using this API, you can collect job applications directly on your website through webhooks.
Prerequisites
To use the Job Postings API, create and configure customer applications. Refer to Create and configure a customer application to create and configure an application for your customer to manage their job posts.
For existing RSC and PJP integrations
If you have a Recruiter System Connect (RSC) or Premium Job Posting (PJP) integration, you already use this API. However, Apply Connect jobs require additional fields because LinkedIn hosts the application experience and delivers applications to partners, unlike PJP or RSC jobs.
Important
- Continue to maintain XML Feeds if you have an Apply Connect integration.
- Send all public jobs to LinkedIn only through this API for your Apply Connect customers.
- Ensure job IDs (
externalJobPostingIdorcompanyJobCode) match across XML feeds, career sites, and API jobs. - Maintain data parity by syncing all available job data from external career sites and XML feeds.
- Send all open, public jobs through the API once you send one job through the API.
Note
LinkedIn will notify you when all customers have migrated to the API and when to disable XML Feeds (typically around 3 months after general access).
Legal requirements for the API
Job Posting legal requirements
- The use of these APIs is restricted to those developers approved by LinkedIn. Reach out to your LinkedIn Relationship Manager or Business Development contact as you will need to meet certain criteria and sign an API agreement with data restrictions in order to use this integration.
- If you are not yet a LinkedIn Talent Solutions Partner, complete the LinkedIn Talent Solutions Partner Request Form.
In addition to any restrictions or obligations contained in a signed API agreement, partner:
- Acknowledges that LinkedIn acts as a passive conduit for the online distribution and publication of job listings and LinkedIn is not responsible for screening or monitoring job listings. Jobs posted to the LinkedIn Service (including via the LinkedIn APIs) may be posted only for lawful purposes by individuals and employers seeking employees. The LinkedIn APIs may not be used to post job listings that violate the restrictions included in the LinkedIn Jobs Terms and Conditions
- Will ensure that its customers agree to the LinkedIn Jobs Terms and Conditions prior to posting any jobs to the LinkedIn Service via partner’s application and shall have a method of keeping track of which of its customers have agreed to the LinkedIn Jobs Terms and Conditions and when, and shall furnish such information to LinkedIn upon request
- Shall not market any job listings to be distributed via LinkedIn or its syndication network as a "free way to post jobs to LinkedIn" or anything substantially similar in any marketing or sales materials
- Acknowledges that in some cases, LinkedIn 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”). 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. LinkedIn reserves the right to require promotion of jobs.
API endpoint
Apply Connect jobs lifecycle
You can perform the following operations on job postings. Pass one of the following values for the jobPostingOperationType field:
- CREATE: To create a new job post.
- CLOSE: To close an existing job post.
- UPDATE: To update a job post by re-posting it with
jobPostingOperationTypeset toUPDATE. - RENEW: To extend a job post’s life by 30 days by re-posting it with
jobPostingOperationTypeset toRENEW.
Try it in Postman
Sample request header
Authorization: Bearer {access_token}
x-restli-method: batch_create
Sample request body
{
"elements": [
{
"externalJobPostingId": "external-job-id-0001",
"title": "Test Job",
"description": "Lorem Ipsum is simply. . .",
"integrationContext": "urn:li:organization:1234",
"listedAt": 1558045934000,
"jobPostingOperationType":"CREATE",
"location": "Enterprise, UT",
"availability": "PUBLIC",
"industries": [
"urn:li:industry:3"
],
"categories": [
"advr"
],
"trackingPixelUrl": "http://localhost:5000/jobs/tracking",
"companyApplyUrl": "http://localhost:5000",
"posterEmail": "test@email.com",
"onsiteApplyConfiguration": {
"jobApplicationWebhookUrl": "https://customer-webhook.com/api/webhook",
"questions": {
"voluntarySelfIdentificationQuestions": {},
"educationQuestions": {
"educationExperienceQuestionSet": {}
},
"workQuestions": {
"workExperienceQuestionSet": {}
},
"additionalQuestions": {
"customQuestionSets": [
{
"repeatLimit": 1,
"questions": [
{
"required": true,
"partnerQuestionIdentifier": "question1",
"questionText": "Please choose the right answer",
"questionDetails": {
"multipleChoiceQuestionDetails": {
"choices": [
{
"symbolicName": "wrong",
"displayValue": "This is the wrong answer"
},
{
"symbolicName": "right",
"displayValue": "This is the correct answer"
},
{
"symbolicName": "right2",
"displayValue": "This is also the correct answer"
}
],
"selectMultiple": false,
"defaultValueSymbolicName": "right",
"preferredFormComponent": "DROPDOWN",
"favorableMultipleChoiceAnswer": {
"favorableSymbolicNames": [
"right",
"right2"
]
}
}
}
}
]
}
]
}
}
}
}
]
}
Note
- Ensure job Ids (
externalJobPostingIdorcompanyJobCode) match across career sites and API jobs. - The
availabilityfield for basic jobs are by default set toPUBLICfor Apply Connect enabled jobs. - The
questionTextfield supports the following formats:- Unordered list
<ul> - List item
<li> - Bold
<b> - Italic
<i> - Links
<a> - Paragraph
<p>
- Unordered list
Request body schema
This API uses:
- The standard Job Posting schema (foundation schema used to post jobs on LinkedIn regardless of the integrated programs)
- The Apply Connect specific
onsiteApplyConfigurationschema to specify questions that applicants must answer to complete the job application
You must also specify a webhook URL in the jobApplicationWebhookUrl field where LinkedIn will POST job applications.
| Type | Field | Value |
|---|---|---|
| Basic Jobs | availability |
This value must be set to PUBLIC for Apply Connect enabled jobs. |
Caution
If the integrationContext field is unavailable for a customer, ensure to provide the companyPageURL field in the payload.
Job Posting foundation schema
For complete details on all job posting fields, refer to job-posting-foundation-schema.
OnsiteApplyConfiguration schema
For complete details on OnsiteApplyConfiguration fields and all question types, refer to onsite-apply-config-schema.
Sample response body
A successful request will return a 200 OK response code, and you will find the simpleJobPostingTask in the response body.
Since Job Postings API is asynchronous, you can refer to Check Job Operation Task Status for task status.
Sample response for success
{
"elements": [
{
"location": "/simpleJobPostings/urn%3Ali%3AsimpleJobPostingTask%3A413d-954e-9b3ed6af71ba",
"status": 202,
"id": "urn:li:simpleJobPostingTask:c9f5-413d-954e-9b3ed6af71ba"
}
]
}
Sample response for error
{
"elements": [
{
"error": {
"message": "ERROR :: /onsiteApplyConfiguration/questions/additionalQuestions/customQuestionSets/0/questions/0/partnerQuestionIdentifier :: field is required but not found and has no default value\n",
"status": 422
},
"status": 422
}
]
}
HTTP status codes and errors
LinkedIn provides standard HTTP status codes and clear messages to help you easily understand errors.
| HTTP CODE | RESPONSE STATUS | ERROR MESSAGE | DESCRIPTION |
|---|---|---|---|
| 400 | 400 | ERROR_INVALID_LISTED_AT_FIELD | The listedAt field with value: 1234567894000 for the job cannot be a future time. An epoch time for future is provided in the listedAt field |
| 401 | 401 | Invalid access token | Access token is tampered |
| 401 | 401 | The token used in the request has expired | The access token used in Authorization header is a valid token but it has expired |
| 403 | 403 | Caller is not authorized to access the jobs for contract: urn:li:contract:{contract_id} | The application used for posting premium job does not belong to the Job posting contract |
| 403 | 403 | Not enough permissions to access: POST /simpleJobPostings | The application does not have enough permissions to use /simpleJobPostings API |
| 422 | 1100 | Required one non-null optional field in /questionDetails |
questionDetails in SimpleTalentQuestionDefinition should have exactly one field. For example, if dateQuestionDetails is present then other fields should not be present |
| 422 | 1101 | PrerequisiteQuestion cannot depend on the response of another PrerequisiteQuestion |
Prerequisite question in prerequisiteQuestionResponse can not be a dependent question. For example, with two questions, Q1 and Q2, if Q2 has Q1 as its prerequisiteQuestionResponse then Q1 should have a null prerequisiteQuestionResponse |
| 422 | 1102 | PrerequisiteQuestion must be present within the same customQuestions set/array |
Prerequisite question in prerequisiteQuestionResponse should be defined within the same customQuestions array |
| 422 | 1103 | Repeatable questions cannot have PrerequisiteQuestion |
If any of the question types in SimpleTalentQuestions has repeatLimit > 1 then all of the questions in it must have a null prerequisiteQuestionResponse |
When Apply Connect task status is FAILED, then errorCode and errorMessage are also present in the response.
| TASK STATUS | ERROR CODE | ERROR MESSAGE | DESCRIPTION |
|---|---|---|---|
| Failed | 150 | LinkedIn Apply update failed | This error occurs due to some issue on LinkedIn and no action is required from the customer side |
| Failed | 1151 | Unable to process questions | This error occurs due to issues with question transformation/validation or due to duplicate question identifiers. Partners are advised to re-validate the question payload. |
| Failed | 1152 | No parent developer application found | This error occurs when the developer application used in job posting does not have a parent developer application in the LinkedIn system. |
| Failed | 1153 | Unable to register jobApplicationWebhookUrl | This error occurs when the job application webhook url is not successfully registered for sending the job applications to the partners |
Related content
To monitor the status of your job postings, refer to Check job posting status.