pinpoint.
Guides and Resources
Connection Setup Guide
Step-by-step instructions to connect your Pinpoint account to Kombo.
View Candidate Sources
How to view and manage candidate sources in Pinpoint.
Supported Features & Coverage
- Models
- Actions
- Features
Users
Users
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| first_name | |
| last_name | |
Jobs
Jobs
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| description | |
| confidential | |
| employment_type | |
| status | |
| visibility | |
| department | |
| post_url | |
| salary_amount_from | |
| salary_amount_to | |
| salary_currency | |
| salary_period | |
| location | |
| custom_fields | |
| integration_fields | |
| remote_url | |
| opened_at | |
| closed_at | |
| remote_created_at | |
| remote_updated_at | |
| contact_id | |
| remote_data |
Job postings
Job postings
Pinpoint’s JSON:API
job_postings resource does not expose a posting-level visibility or status. We therefore sync job postings from the public postings.json career-site feed, which only lists publicly visible postings. Internal postings never appear in that feed and are consequently not synced.| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description_html | |
| status | |
| visibility | |
| url | |
| job_id | |
| remote_data |
Candidates
Candidates
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| first_name | |
| last_name | |
| source | |
| phone_numbers | |
| email_addresses | |
| social_media | |
| location | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Application Stages
Application Stages
Pinpoint exposes application stages as part of the job API response. Kombo will only be able to reference application stages if reading jobs is enabled in the scope config.
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name |
Applications
Applications
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| outcome | |
| current_stage_id | |
| job_id | |
| candidate_id | |
| screening_question_answers | |
| remote_url | |
| remote_created_at | |
| remote_updated_at | |
| remote_data |
Screening questions
Screening questions
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description | |
| format | |
| category |
Interviews
Interviews
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| starting_at | |
| ending_at | |
| application_id | |
| remote_data |
Roles
Roles
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| remote_label | |
| scope | |
| unified_type |
Job-specific application stages
Job-specific application stages
| Field | Notes |
|---|---|
| index | |
| job_id | |
| stage_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Job-specific screening questions
Job-specific screening questions
| Field | Notes |
|---|---|
| index | |
| required | |
| precondition_question_id | |
| precondition_options | |
| job_id | |
| question_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Job user role assignments
Job user role assignments
Pinpoint exposes 2 relations for the job
- hiring_manager_user (shown as “Public Hiring Manager Profile” in the UI) maps to unified type
HIRING_MANAGER - recruitment_manager_user (shown as “Recruitment Manager” in the UI) maps to unified type
RECRUITER
| Field | Notes |
|---|---|
| job_user_id | |
| role_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Job hiring team members
Job hiring team members
| Field | Notes |
|---|---|
| roles | |
| job_id | |
| user_id | |
| id | |
| changed_at | |
| remote_deleted_at |