Job Posting API - Development Tools
Use the resources in the development tools to help expedite your development process. If you have any questions, please raise a support ticket on Zendesk platform and reach out to us.
We provide below resources:
- Project Plan describes different stages of Job Posting API development and estimated timeline to help create project plans for Job Posting API integration
- Postman Collection contains all the APIs required for Job Posting API integration. Development teams can use the Postman collection for reference while developing their code. It is fully functional and covers all the APIs and can be used as a playground to understand them in detail and try them out before starting any development activities
Project Plan
Job Posting API is a light weight offering from LinkedIn. This is also a foundation element that all LTS partners should first develop with. To help Project Managers and Developers with the planning, timelines and create checkpoints on different activities, we have created a Project Plan mentioned below.
Milestones definitions for Job Posting API Integration Project Plan as follows:
| Milestone | Description |
|---|---|
| Self-Serve access provided by LinkedIn | 1. Request Access 2. If your partnership request gets approved, LinkedIn's Business Development point of contact reaches out to you and proceeds with a contract 3. Please create a developer application on LinkedIn's Developer platform and submit a ticket on Zendesk platform requesting to provision access 4. LinkedIn will provision your developer application that should be used for testing and also create and provide necessary test environment artifacts. These details are shared with you as response to your Zendesk ticket 5. After the provisioning request is submitted, LinkedIn takes three days time to complete the same |
| Program Overview | 1. Partner developers and project managers should go through Job Posting API and set up and discuss timelines with the LinkedIn Business Development team to start development 2. They should also use this time to get any questions and doubts resolved by filing tickets on Zendesk partner support platform |
| Development and Testing | 1. Develop functionality for Job Posting API 2. Ensure that integration adheres to Foundation Schema. In case you are building an extension on top of the Foundation Schema, please ensure development against specific schema extension definitions 3. Ensure to test out all Certification use cases as applicable to your integration 4. This should approximately take one month of development effort |
| Final Certification Review and Approval | 1. Partner should submit a recording covering all applicable certification use cases by creating a support ticket on Zendesk platform 2. LinkedIn Business Development and Partner Engineering Team will review all the certification videos submitted and provide feedback for corrections if any 3. Once, there are no more corrections and integration looks compliant and correctly implemented, the partner or customer is certified by LinkedIn and necessary privileges will be given to the production application 4. Post submission of the recording, certification should take a week approximately |
| General Availability | 1. Partner should configure production application in their production environment and perform quality testing independently 2. When production changes are ready to be pushed live, the partner can work with LinkedIn's Business Development point of contact on any marketing collaterals and go live date |
Postman Collection
You can use the Postman collection for Job Posting APIs and try out all APIs for different use cases. Postman is a free-to-download tool for making HTTP requests.
Important
Please note that Postman is an independent entity and is not affiliated with LinkedIn. LinkedIn is providing the following resources to support your use of the Postman services but ultimately, any use of third party services, such as the Postman Services, is at your own discretion and risk.
LinkedIn does not endorse or vet the Postman services and is not responsible for any damage or loss of data resulting from your use of third party services. Nothing herein shall restrict LinkedIn's ability to enforce all of its rights under its agreements with you.
The easiest way to get started using the Job Posting APIs is to use our Postman collections. We have posted our APIs in LinkedIn's Postman workspace. If you prefer, you can explore our API with other tools like curl.
Explore Postman Collection
The below button will take you to LinkedIn's Postman's workspace. Select the workspace with name LinkedIn Talent Solutions. You will find the Job Posting API collection in it.
How to Use Postman Collection
Job Posting API Postman Collection Environment Variables
In order to start using your Job Posting API Postman collection, you need to first configure your environment variables. These variables are defined in the Job Posting environment within the Environment section of Postman. Please set the value for these variables and click Save.
Note
Ensure that you select Job Posting environment. To know more about selecting the environment, refer to this Postman article
Below is the list of variables:
| Variable Name | Description |
|---|---|
| client_id | Client id of partner's application. This is used to get the access token to be able to call Job Posting APIs |
| client_secret | Client secret of partner's application. This is used to get the access token to be able to call Job Posting APIs |
| company_id | Organization(company) id value for customer. This appears in integration_context of type urn:li:organization:id |
| contract_id | Contract id present in contract urn of type urn:li:contract:id. This is required only if you are also building with Promoted Jobs Extension Schema else can be left blank |
| external_job_posting_id | Unique job id within the partner system |
How to get Access Token to Execute APIs
Authorization is configured at the collection level. Select the Job Posting collection and click the Authorization tab. Ensure that you have defined the values for the client_id and client_secret variables in the Job Posting environment.
To request an access token, click Get New Access Token. This calls LinkedIn's authorization service to fetch new access token. Once Postman receives the access token, click Use Token. This access token is used for all API calls automatically within the collection.
In case the token expires, you can generate the access token again by following the above steps.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for