Module 4 - PJP Widget and Enabling Customers via widget
Upon completing development, to ensure official certification of Module 4, 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-D-01 | Demonstrate customer opt-in via PJP onboarding widget with contract and Default job poster |
JP-D-02 | Demonstrate how the PJP onboarding widget callback response is managed and customer is notified of their enablement state |
JP-D-03 | After a customer is initiated PJP onboarding via the PJP onboarding Widget, a JS-callback is returned from the same widget. Partner needs to make an /ATSIntegration call using the returned parameters. Demonstrate how this is done? |
JP-D-04 | Demonstrate Global Customer Settings for: Company, Contract for created application ID |
JP-D-05 | Do you have customers with multiple contract_Ids? - ATS should make provision to onboard multiple contracts for the same company. - For multiple contract_ids for a same company_id, use same child application_id. |
JP-D-06 | For customers with multiple contracts, How customers can identify "ENABLED" contracts? |
JP-D-07 | Demonstrate How customers can choose the contract and company_ID to post a job |