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.
August 2024 -- Change Log
- Updated certification requirements to add Module 8 - Sync CRM ACLs (CRM-155 - CRM-161).
- Updated certification requirements with additional certification items for Module 5 - Data Deletion related to ACL management (CRM-162 - CRM-165)
July 2024 -- Change Log
- Updated Sync Candidate Resumes with a new example that omits the
blobTtl
field. - Updated CRM Connect Overview to reference Module 8 - Sync ACLs.
- Added ACL Overview.
- Added Sync CRM ACLs.
- Added Sync CRM ACL Assignees.
- Updated Sync Pipelines with versioning details and new
accessRestricted
field. - Added Bind Customer Users.
March 2024 -- Updates to atsCandidates and Various Updates
- Updated Sync Candidates to indicate that the
firstName
field is required - Updated Sync Candidates to add
doNotContact
field - Updated Sync Candidates updated phone number and address fields to indicate they are required but can be empty
- Changed Stubprofile
emailAddress
field lists array of email to type string. - Documentation now linked to public TOC.
- Updated Retrieve CRM Exported Candidates to indicate that
externalPipelineId
is a required field. - Fixed various types in CRM Customer Configuration and Sync CRM Interactions docs
November 2023 - Various Updates
- Removed
tcrmStageId
as a field from the PUT example in Sync Candidate Pipelines via Batch Update. - Clarified requirements for defining filenames for uploaded resumes in Upload Resume File.
- Clarified that Module 2 - Sync TCRM Candidate Pipelines in the certification test cases includes validation of stage syncing for a candidate.
- Modifications have been made to sample apps to support CRM Connect, for more information see Sample HTML Applications for Talent CRM Connect.
October 2023 - CRM One Click Export Limits
- Limits for CRM One Click Export updated to 300 requests per month per seat.
September 2023 - Various Updates
Made changes to the documentation including these updates:
- Clarified in sync CRM candidates documentation that attaching a person URN should use
BATCH_UPDATE
method.BATCH_UPDATE
now supports supplyingmanualMatchedMember
. - Updated Sync Candidate Resumes to specify
x-linkedin-id
instead ofx-restli-id
as the header which contains the createdhireMediaUrl
. - Added a clarification to each Module 2 page indicating that all historical data must be synced upon activation.
- Clarified that InMail stub profiles will only be populated when members share contact info.
- Added
SMS
as a supported interaction type in synced interactions. - Clarified that the RSC Schema is also for CRM Connect. Added note that
alternateLocations
are not supported for jobs synced for RSC and CRM Connect. - Added Talent CRM Connect Error Handling to documentation and updated side bar links.
- Moved certification test case CRM-133 from Module 7 to Module 3.
- Added new certification requirements:
Rule | API Requirements | Expected Result |
---|---|---|
CRM-036 | Confirm that all candidate records have been synced to LI as part of historical sync. | Gross number of candidates that exist in the CRM matches the number in LI. |
CRM-042 | Confirm that all candidate resume records have been synced to LI as part of historical sync. | Gross number of candidate resumes that exist in the CRM matches the number in LI. |
CRM-052 | Confirm that all pipeline records have been synced to LI as part of historical sync. | Gross number of pipelines that exist in the CRM matches the number in LI. |
CRM-063 | Confirm that all pipeline stage records have been synced to LI as part of historical sync. | Gross number of pipeline stages that exist in the CRM matches the number in LI. |
CRM-073 | Confirm that all candidate pipeline records have been synced to LI as part of historical sync. | Gross number of candidate pipelines that exist in the CRM matches the number in LI. |
CRM-084 | Confirm that all interaction records have been synced to LI as part of historical sync. | Gross number of interaction records that exist and should be synced from the CRM matches the number in LI. |
CRM-109 | Demonstrate the deletion of a purged members. | Purged members that customers choose to delete have data retrieve from LI removed from the CRM. |
CRM-150 | Partner is in compliance with all Terms of Service and partnership agreements. | Partner is not violating partnership agreements or Terms of Service. Any remediation plans defined to resolve violations have been completed. |
July 2023 Module 7 API Documentation Available and Other Minor Updates
Published the following API docs:
- Retrieve Recruiter Contract Seatholders (/seatsV2)
- Retrieve InMail History (/conversationEvents)
- Retrieve InMail Stub Profiles (/mailStubs)
Made the following minor revisions:
- Updated Retrieving Closed Candidate Profiles documentation to describe expected partner behavior:
Our CRM partners must query this endpoint periodically (at least once in 30 days) and notify end customers that they may need to delete the data that appear within this endpoint from their records if they do not have a legal basis to continue processing it.
- Updated Upload Resume File to remove
x-ambry-content-type
parameter requirement from file upload step.
July 2023 tcrmPipelines, API Versioning Announcement
- tcrmPipelines has been updated to include the
private
optional field. See documentation link for more details
Versioning Announcment
- In order to release new API versions to incorporate feedback and new enhancements, future endpoint updates will only be released on LinkedIn's verisoning solution, which can be accessed with a new base URL and version header:
Old Base URL | New URL |
---|---|
https://api.linkedin.com/v2/ |
https://api.linkedin.com/rest/ |
- Consuming the new versioned endpoint will also require sending a
LinkedIn-Version
header in requests, populated with a version identifier. - Old versions of endpoints will continue to function in the state in which they exist today until deprecation.
- In order to facilitate easy migration, all partners are asked to support easy configuration switch base URLs and conditionally supply a version header, so that new versioned endpoints can be quickly adopted. Support for rapid migration will be considered as certification criteria (see new certification section here).
- LinkedIn will notify partners as new versions are available through communications and in our documentation release notes.
June 2023 atsCandidates, Profile Plugin, Onboarding Configuration Plugin Updates
linkedInProfileUrl
has been added as a valid field in the request body (details)- Profile Plugin documentation has been updated to reflect production release details
- Module 1 - Configure Customer Applications & CRM Integrations has been completely updated to reflect customer onboarding requirements
- The atsCandidates validation rules have been updated with the following changes:
Field | New Validation Rules |
---|---|
addresses | All fields are optional but must comply with the following rules:
|
currentCompanyName | If specified, string value cannot be empty or blank spaces. |
currentJobTitle | String value cannot be empty or blank spaces. |
emailAddresses | 30 email addresses max. |
externalProfileURL | String value cannot be empty or blank spaces. |
firstName | String value cannot be empty or blank spaces. |
linkedInProfileUrl | String value cannot be empty or blank spaces. |
phoneNumber | Format must follow com.google.i18n.phonenumbers standard. At most 30 phone numbers can be provided. |
March 2023 Sync APIs and CRM One-Click Export Available
Talent CRM Sync APIs are available for adoption. /exportedCandidates
service that powers CRM One-Click Export is also available.