Linking Huntr as a source
This source is currently in alpha. The interface and available tables may change.
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
The Huntr connector syncs your recruiting and job search tracking data into PostHog, including members, advisors, candidates, jobs, job posts, employers, activities, and actions.
Creating a Huntr access token
Huntr uses Bearer token authentication with an organization access token. The token grants read access to your organization's data.
- Log in to your Huntr organization admin dashboard.
- Navigate to the API or access token settings.
- Generate an organization access token.
- Copy the token.
For more details, see Huntr's API documentation.
Linking Huntr
- Go to the Data pipeline sources page in PostHog.
- Click + New source and then click Link next to Huntr.
- Paste your Huntr organization access token.
- Click Next, choose the tables you want to sync, and then click Import.
Once the sync completes, you can query your Huntr data directly in PostHog.
Configuration
| Option | Type | Required |
|---|---|---|
Organization access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
members | A member (job seeker) whose job search the organization is following in Huntr. | Full refresh | — | — |
advisors | An advisor — an organization team member who manages and supports job seekers. | Full refresh | — | — |
candidates | A candidate profile managed within the organization. | Full refresh | — | — |
jobs | A job a member is tracking on their board (a saved role and its application progress). | Full refresh | — | — |
job_posts | A job post published or shared by the organization to its members. | Full refresh | — | — |
employers | An employer tracked by the organization. | Full refresh | — | — |
activities | An activity — an interview, task, or event linked to a member's job search. | Full refresh | — | — |
actions | An action recorded against a member or job (Huntr's successor to the deprecated events resource). | Full refresh | — | — |
activity_categories | A category that classifies an activity, such as Apply, Phone Interview, or Offer Received. | Full refresh | — | — |
tags | A tag the organization created to label records such as job posts. | Full refresh | — | — |
candidate_action_metrics | Per-candidate counts of an action type that employers performed, such as viewing the candidate profile. | Full refresh | — | — |
Sync modes
All Huntr tables use full refresh syncing — data is completely re-downloaded on every sync. The Huntr Organization API doesn't expose reliable updated_after filters across its endpoints, so incremental syncing is not supported.
Available datasets and endpoints
| Dataset | Endpoint path | Sync mode | Primary key |
|---|---|---|---|
members | /members | Full refresh | id |
advisors | /advisors | Full refresh | id |
candidates | /candidates | Full refresh | id |
jobs | /jobs | Full refresh | id |
job_posts | /job_posts | Full refresh | id |
employers | /employers | Full refresh | id |
activities | /activities | Full refresh | id |
actions | /actions | Full refresh | id |
All endpoints use the Huntr Organization API (api.huntr.co/org).