Partager via

Module 5 - Basic and Premium Job Posting

  • Article

Upon completing development, to ensure official certification of Module 5, please review each of the test cases mentioned below. To ensure an efficient meeting or review of the recorded demo shared via Zendesk, 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-E-01 There should be a single customer/child application for a customer's Basic & Premium job post related to one company_id
JP-E-02 Demonstrate the ability to upgrade a Basic job to a Premium job. Steps to demonstrate this:
- Post a Basic job
- Upgrade the Basic job using the guide and the same externalJobPostingId
- Wait for the /simpleJobPostingTasks API to reach a terminal state
- Check the /jobPostingStatus API to determine the job listing type (Basic/Premium) and URL
- Display the job URL and listing type to the customer in the ATS UI.
JP-E-03 Demonstrate the ability to downgrade a Premium job to a Basic job Steps to demonstrate this:
- Post a Premium job
- Downgrade the Premium job using the guide and keeping the same externalJobPostingId
- Wait for the /simpleJobPostingTasks API to reach a terminal state
- Check the /jobPostingStatus API to determine the job listing type (Basic/Premium) and URL
- Display the updated job URL and listing type to the customer in the ATS UI.
JP-E-04 Demonstrate the error handling while upgrading a job from Basic to Premium when the customer app is not configured with PJP Steps to demonstrate this
- Do not onboard the PJP Widget using the customer app's child-app-id-1
- Post a Basic job using child-app-id-1
- Upgrade the same Basic job to Premium
- If the upgrade fails, handle the error gracefully and guide the customer through the process.
JP-E-05 Demonstrate the expiry date handling and show how recruiter customers are made aware of the expiry date updation, if any. Steps to demonstrate this:
- When upgrading from Basic to Premium, the default expiry period is set to 30 days. If the 'expireAt' field value is passed via payload then that value will be set; it can be extended to a maximum of 90 days. If the ATS platform displays the job's expiry date to customers, any changes to the expiry date must be reflected in the UI.
- When downgrading from Premium to Basic, the default expiry period is set to 180 days. If the 'expireAt' field value is passed via payload, it will be set accordingly. It is recommended to set the 'expireAt' field value for Basic jobs to no more than 180 days.
JP-E-06 Demonstrate the LI job-url change handling and show how recruiter customers are made aware of the job-url updation. Steps to demonstrate this:
- An inline downgrade will result in a change to the LI job URL. It is important to ensure that the new job URL is displayed in the ATS UI for customers to reference.