Huntr

Huntr is a job tracking and career placement platform designed for organizations—such as universities, bootcamps, career coaching firms, and workforce development programs—that support job seekers in their employment searches. Through Huntr's Organizational API, administrators and advisors can programmatically access data on their members' job search activity, including the jobs, employers, and events that members track within their Huntr boards. Huntr provides a centralized view of job seeker progress, enabling organizations to measure placement outcomes and identify where members may need additional support.

Power end-to-end data operations for your Huntr API with Nexla. Our bi-directional Huntr connector is purpose-built for Huntr, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Huntr or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Huntr workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Huntr's Organizational API is available to organizations using Huntr Advisor—Huntr's career placement platform for universities, bootcamps, career coaching firms, and workforce development programs. To use this connector, your organization must have an active Huntr organizational account with API access enabled.

Obtain Your Huntr Organization Access Token

Nexla authenticates to the Huntr API using an Organization Access Token, which is a long-lived Bearer token associated with your Huntr organizational account. This token grants access to your organization's member, job, employer, and event data through the Huntr API.

To obtain your Organization Access Token:

1. Sign in to your Huntr organizational account at huntr.co.

2. Navigate to your organization's admin settings. The token generation option is located in your organization's API or developer settings section within the admin dashboard.

3. Generate a new Access Token. Copy the token value immediately and store it securely — you will need to paste it into Nexla when creating your credential.

Important

Your Organization Access Token carries full read access to your organization's member and job data. Keep the token secure and do not share it in publicly accessible locations such as code repositories or client-side applications.

Additional details about the Huntr Organization API and access token management are available in the Huntr Organization API documentation.

Authenticate

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Huntr Organization Access Token in the API Token field. This is the Bearer token obtained from your Huntr organizational admin dashboard, as described in Prerequisites above. The token authenticates Nexla with the Huntr API and authorizes access to your organization's data.

4. Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with a new data source.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Huntr connector tile, then select the credential that will be used to connect to the Huntr account, and click Next; or, create a new Huntr credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Huntr endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

List Members

This endpoint retrieves a list of all members (job seekers) in your Huntr organization. Use this endpoint to track which job seekers are enrolled in your program and to access their profile information, including contact details and the date they joined your organization.

• This endpoint automatically retrieves all members associated with your organization. No additional parameters are required to fetch the full member list.
• Results are paginated using Huntr's cursor-based pagination. Nexla handles pagination automatically, fetching all available pages so your Nexset contains a complete record of your organization's members.
• Each member record includes identifiers, profile information, and organizational metadata that can be used to join with job and event data from other Huntr endpoints.

Member data reflects the current state of your Huntr organization roster. For job search activity associated with each member, use the List Jobs or List Job Events endpoints.

List Jobs

This endpoint retrieves all job applications tracked by members of your Huntr organization. Use this endpoint to analyze your members' job search activity, including the companies they are applying to, the stages of their applications, and timestamps for key application milestones.

• This endpoint returns all job records across all members in your organization. Each record includes details such as job title, employer, application stage, and associated member information.
• Results are paginated automatically by Nexla, ensuring all job records are retrieved regardless of the total volume of data.

• The job data returned by this endpoint can be used to:

  • Measure job application volume across your member cohort.
  • Identify which employers your members are most actively pursuing.
  • Track the progression of applications through different hiring stages.
  • Build placement rate and outcome reports for your organization.

Job records are created by members on their individual Huntr boards. Data reflects activity as recorded by your members and their advisors within the Huntr platform.

List Employers

This endpoint retrieves all employer records associated with job applications tracked within your Huntr organization. Use this endpoint to build a picture of the companies your members are engaging with during their job search, and to identify which employers are most frequently targeted by your member cohort.

• This endpoint returns employer records linked to job applications in your organization. Each record includes employer name, location, industry, and other profile information where available.
• Employer records are generated automatically when members add job applications referencing a specific company. The same employer may appear across multiple member job records.
• Use employer data in combination with job application data to report on the breadth and depth of your members' employer outreach.

List Job Events

This endpoint retrieves all job events (activities) associated with job applications tracked within your Huntr organization. Job events represent discrete activities in a job search, such as phone screens, interviews, offers, and rejections. Use this endpoint to track the progression of your members' job searches at a granular level.

• This endpoint returns all job event records across your organization. Each record includes the event type, the associated job and member, and timestamps for when the event occurred and was recorded.
• Results are paginated automatically by Nexla to ensure complete data retrieval.

• Common use cases for job event data include:

  • Tracking how many interviews your members are securing per application.
  • Measuring time-to-offer or time-to-placement across your member cohort.
  • Identifying patterns in offer acceptance and rejection rates.
  • Generating activity reports for advisors and program managers.

Job events are recorded by members and advisors within Huntr. The availability and completeness of event data depends on how consistently your members update their job boards. For additional details about event types supported by the Huntr API, refer to the Huntr Organization API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Huntr data sources can also be manually configured to ingest data from any valid Huntr API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Huntr's Organization API is read-only — use the GET method for all requests. The base URL is https://api.huntr.co/org; append the resource path to target member (/members), job (/jobs), employer (/employers), or job event (/job-events) data. Each endpoint wraps its records in a top-level data array, so set the path to data to $.data[*]; the sibling next cursor field can be captured as metadata with $.next if you want to preserve pagination context with each record. You do not need to add an Authorization header manually — the Bearer token from your Huntr credential is included automatically in all API requests.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Huntr data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.