Feature Requests

The "education" object in Person records contains canonical school data for each record's education experience, with a " school.id " assigned for each canonicalized school. Since most/all of these schools have corresponding PDL company records, it would be helpful to also have the PDL company ID as an included field in the school object, enabling users to more easily join information from the company table onto the education data.

Other offerings provide this

I am interested in receiving more frequent updates of the job posting data, rather than the current monthly delivery.

Create a Skill Taxonomy to help define interrelationships amongst skills (i.e. programming languages > javascript > React == ReactJS). This is useful for mapping and understanding the landscape of skills.

Introduce list management endpoints (e.g., POST /lists, POST /lists/{id}/contacts) and support an exclude_list_ids parameter in the /person/search API to filter out known contacts without passing large arrays of individual IDs. This will reduce payload sizes, improve query performance, and simplifies the client-side integration

I would like to have recruiter information included in the job posting data, similar to what is available on LinkedIn, where the actual person assigned to the recruiting process is visible.

Allow bulk requests to the Job Title / Skill Enrichment API

Allow clients to prioritize or surface to PDL the profiles (URLs) that they are interested in seeing refreshed. PDL would gather the data actively upon request and update them within 1-2 data releases.

Information on the technology and services being used at a company.

Supporting more frequent data releases such as daily, weekly, bi-weekly.