Skip to main content

Huntr Data Source

The Huntr connector enables you to ingest job search activity data from your Huntr organizational account into Nexla. Use this connector to pull member data, job applications, employer records, and job events tracked by your organization's members — making it easy to analyze placement outcomes, measure advisor effectiveness, and build data pipelines for workforce reporting. Follow the instructions below to create a new data flow that ingests data from a Huntr source in Nexla.
huntr_api.png

Huntr

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Huntr connector tile from the list of available connectors. 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.

  3. In Nexla, Huntr data sources can be created using pre-built endpoint templates, which expedite source setup for common Huntr API endpoints. Each template is designed specifically for the corresponding Huntr endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Huntr sources can also be configured manually, allowing you to ingest data from Huntr endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Huntr endpoints. Each template is designed specifically for the corresponding Huntr endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    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.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Huntr data sources can be manually configured to ingest data from any valid Huntr API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Huntr sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Huntr API from the Method pulldown menu. The Huntr Organization API is a read-only API — the appropriate method for all standard data retrieval calls is:

    • GET: For retrieving member, job, employer, and event data from the API.

API Endpoint URL​

  1. Enter the URL of the Huntr API endpoint from which this source will fetch data in the Set API URL field. Huntr's Organization API base URL is https://api.huntr.co/org. Append the specific resource path to the base URL to target the desired data. For example:
    • https://api.huntr.co/org/members — retrieves all members in your organization.
    • https://api.huntr.co/org/jobs — retrieves all job applications tracked by your members.
    • https://api.huntr.co/org/employers — retrieves all employer records associated with your members' job applications.
    • https://api.huntr.co/org/job-events — retrieves all job events (activities) associated with your members' job applications.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. Additional endpoint details are available in the Huntr Organization API documentation.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Date/time macros are particularly useful when querying Huntr endpoints that accept date-range parameters for filtering records by creation or update timestamps.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are useful when you need to pass Huntr member IDs, job IDs, or other identifiers from one Nexla data source into the URL of another — for example, fetching job events for a specific member retrieved from the List Members endpoint.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data that will be returned by the API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

The Huntr API returns list results in a JSON object with a data array containing the records and a next field for cursor-based pagination. To extract only the records from the response, specify the path to the data array.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.data[*] to access the array of records returned by a Huntr list endpoint).
    Path to Data Example:

    For Huntr list endpoints, the response includes a top-level data array containing the relevant records. Enter $.data[*] in the Set Path to Data in Response field to configure Nexla to treat each element of that array as an individual record.

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

    PathSuggestions.png

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

For example, when retrieving a list of Huntr jobs, the API response includes a next cursor field for pagination and potentially other summary fields alongside the data array of job records. If you want to preserve this pagination metadata with each record in your Nexset, you can specify the path to it here.

Metadata paths are particularly useful for preserving API response context like pagination cursors or response-level fields that provide useful context alongside individual records.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers may be required for API versioning or content type specifications.

    You do not need to include the Authorization header here — the Bearer token from your Huntr credential is automatically included in all API requests by Nexla.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, 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.