Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Pinpoint: Missing Candidate Entity and Link

Answered
Paul Monk User

Connector name:

Pinpoint

Table name:

Candidate

API documentation link:

https://developers.pinpointhq.com/reference/get-candidates

https://developers.pinpointhq.com/reference/get-applications

Additional details:

The `application` table the connector produces has `job_id` and `stage_id` foreign keys but no `candidate_id`, and there is no candidate entity in the synced schema. Pinpoint exposes an application→candidate relationship; it returns the candidate id (and record, type `candidates`) under `include=candidate`:

Please map the application→candidate relationship so `application.candidate_id` is populated, and sync the candidate as its own table (it is a distinct `candidates` entity, separate from `job_seekers`).

This is meaningful data for a recruitment platform connector, as "candidate" is a key entity.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Syead Mujtaba Imam Rizwi Fivetranner

    Hi Paul,

    Thank you for taking the time to share your detailed feature request regarding the Pinpoint connector. We appreciate your input and the clarity you provided on how this enhancement would improve the data schema.

    I’m pleased to inform you that your request has been added to our backlog. We will prioritize it based on overall demand and its potential impact on our users. 

    We understand the importance of having a complete and accurate representation of the candidate data within recruitment platforms, and we will keep you updated with any progress or developments regarding this feature.

    Thank you once again for your valuable feedback and for helping us improve our services.

    Best regards,  
    Syead Mujtaba Imam Rizwi