Description:

We are currently evaluating Fivetran as our centralized ELT solution to integrate Pinpoint ATS data into Snowflake. This will serve both internal operations and multiple client implementations. While testing the Pinpoint connector, we discovered that two essential datasets are missing:

• Candidate survey data (from the /v1/candidate_surveys endpoint)

• Custom field definitions (from the /v1/custom_fields endpoint)

These datasets are critical for reporting, analytics, and operational visibility across several recruiting workflows. We would like to formally request these endpoints be added to the Pinpoint connector.

Business Case

We are supporting multiple clients who rely on Pinpoint ATS. Our approach involves replicating all recruitment-related data into Snowflake and building out dashboards in Power BI to surface operational insights to HR, Talent Acquisition, and executive teams.

1. Candidate Survey Data (/v1/candidate_surveys)

Why it’s important:
Candidate survey responses provide the most direct measurement of candidate experience. This data informs:

• Satisfaction scoring (including Net Promoter Score)

• Quality assessment of recruiters and interview processes

• Identification of candidate pain points

• Employer brand monitoring and improvement

Use cases:

• Monthly reporting on candidate experience KPIs

• Comparative dashboards across departments, roles, or timeframes

• Root-cause analysis of negative feedback trends

Impact of not having it:
Without this dataset, we will be forced to create and maintain a parallel pipeline via custom API integration, which adds cost and complexity, undermining the unified ELT value that Fivetran promises.

Endpoints needed:

• GET /v1/candidate_surveys – List of submitted surveys

• GET /v1/candidate_surveys/{id} – Details of a single survey

These endpoints have been successfully tested using Postman. They do not appear to support a visibility parameter (unlike other endpoints such as /v1/applications), so no filter appears necessary for full data access.

2. Custom Field Definitions (/v1/custom_fields)

Why it’s important:
Custom fields in Pinpoint are used by customers to model business-specific data such as approval statuses, regional flags, or internal scoring mechanisms.

Use cases:

• Mapping field IDs to user-friendly labels and types

• Supporting flexible schemas that vary across clients

• Rendering dynamic reports without manual field dictionaries

Impact of not having it:
Fivetran already syncs data from endpoints like APPLICATION_CUSTOM_ATTRIBUTES_DATA and JOB_CUSTOM_ATTRIBUTE_DATA, but without access to the field definitions themselves, the values are contextless. We would be forced to maintain manual field maps, which become quickly outdated and error-prone.

Endpoints needed:

• GET /v1/custom_fields – List of field definitions

• GET /v1/custom_fields/{id} – Metadata for a specific field

This data has also been validated using Postman and is available.

🔧 Summary of Technical Requirements

📈 Strategic Value

• Adds two critical datasets for complete recruiting analytics

• Enables use cases that span multiple clients and organizational units

• Reduces need for custom API pipelines

• Strengthens Fivetran’s appeal for customers using Pinpoint ATS at scale

We would be happy to share examples, sample dashboards, or join a call to discuss further if needed.

Thank you for your consideration.