Module 3 - Create and Manage Jobs
Upon completing development, to ensure official certification of Module 3, please review each of the test cases mentioned below. To ensure an efficient meeting, please review all appropriate documentation and send technical questions to your Business Development and/or Partner Engineering representative beforehand.
Note
- The Certification Demo can be scheduled with your LinkedIn Business Development point of contact in any order of the above modules as and when development & testing is complete.
- In the demo, all the module-specific test cases should be covered. If few test cases are not applicable for your integration, call them out and notify proactively if possible to your business development point of contact.
- LinkedIn will certify based on the complete coverage of test cases in the certification demos.
- Upon successful certification, LinkedIn will provision your Production API Key
| Rule | API requirements |
|---|---|
| JP-C-01 | Demonstrate the ability for a customer to create a Job Requisition in your ATS. |
| JP-C-02 | Demonstrate job attribute mappings are based on LinkedIn pre-defined values (ie. categories, experience level, industries, employment status). Confirm if no mapping exists with LinkedIn's pre-defined values then raw string values are send instead of using existing enum values like 'OTHER' or 'NOT_APPLICABLE' value. Mandatory Fields: Company Name (provide companyID too if you have), Description, Location, Title, CompanyApplyUrl, ListedAt, ExternalJobPostingId, JobPostingOperationType |
| JP-C-03 | Demonstrate ability to post a remote location job or define workplacetype. Required if workplace types are presented on career sites |
| JP-C-04 | Demonstrate the ability to view or display the successfully created LinkedIn job posting URL. |
| JP-C-05 | Demonstrate the ability of a customer to update job properties like description/title after a job is created and synced on LinkedIn. Show the change reflected in the LinkedIn website for job posting |
| JP-C-06 | Demonstrate the actions that trigger renewing the job posting on LinkedIn |
| JP-C-07 | Demonstrate the actions that trigger closing the job posting on LinkedIn |
| JP-C-08 | Demonstrate Error Scenario |
| JP-C-09 | Demonstrate or explain retry logic and logging for failed job sync requests. - For failure, LinkedIn needs ATS to store both request & response payload in full including headers. - For any failure if any LI assistance is needed, LI will request to furnish the full request/response and X-LI-UUID response header value. |
| JP-C-10 | ATS should enforce strict minimum and maximum length checking of various fields those were inputted by the customer and the same was passed to the API via as a payload. Demonstrate that title with length less than 50 characters and Description less than 150 characters are failing at ATS side, and no LI API call was made. - If ATS couldn't implement such restriction at ATS side, show us the error handling at API level. |
| JP-C-12 | Demonstrate that the job is posted against a location-type as mentioned in the API schema |
| JP-C-13 | Demonstrate that offsite apply urls are source attributed to LinkedIn. 'companyApplyUrl' field is used to mention this source attribution. |
| JP-C-14 | Demonstrate retrieving the current job posting status and displaying status in the ATS. Check Job Posting Status API |
| JP-C-15 | Demonstrate that the externalJobPostingId for a job is unique among all jobs submitted across all child applications. |
| JP-C-16 | Demonstrate that multiplexing is used or that the tile title, externalJobPostingId, company and location will all be unique for all job postings posted via API. Confirm whether multiplexing or uniqueness is utilized to avoide deduplication. |
| JP-C-17 | If RSC is implemented, demonstrate that job postings and job requistions are being sent for each public job, and job requisitons are being sent for private jobs. |