Fountain

Fountain is a high-volume hiring and applicant-tracking platform used to source, screen, interview, and onboard hourly and frontline workers at scale. The Fountain connector uses the Hire API to read applicants, openings, stages, locations, and workers, and to create or update applicant records from your Nexla flows.

Power end-to-end data operations for your Fountain API with Nexla. Our bi-directional Fountain connector is purpose-built for Fountain, 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 Fountain or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Fountain 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

Before creating a Fountain credential, you need a Fountain API access token. Fountain authenticates every Hire API request with a per-account token passed in the X-ACCESS-TOKEN request header.

To obtain your Fountain API token, follow these steps:

1. Sign in to your Fountain dashboard using an account that has administrator access.

2. Click your account name in the top-right corner of the dashboard, and select Company Settings.

3. On the API page under Developer Settings, click the Show API Keys button to reveal your account's API token.

4. Copy the API token and store it securely, as you will need it to configure your Nexla credential.

If no API settings are available in your account, contact Fountain support to request API access before proceeding. Fountain also offers a Trusted Party API Key that is scoped only to creating applicants, which can be shared with third parties without exposing sensitive data.

For complete details on authentication and available endpoints, see the Fountain API Reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Fountain API access token, found under Account Settings > API in the Fountain admin dashboard.

Create a credential in Nexla

1. After selecting the data source/destination 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 Fountain API access token in the API Key field. This token is sent in the X-ACCESS-TOKEN header for all requests to the Fountain API and must be kept confidential.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

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 Fountain connector tile, then select the credential that will be used to connect to Fountain, and click Next; or, create a new Fountain 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 Fountain 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 Applicants

List all applicants (candidates) with optional filters by funnel, location, or stage.

• This endpoint returns paginated results. Nexla automatically follows the cursor-based pagination to retrieve all available applicant records.

Get Applicant

Retrieve a single applicant by ID.

• Provide the applicant's external ID in the Applicant ID parameter to fetch that specific record.

List Applicant Transitions

Retrieve the stage-transition (funnel movement) history for an applicant.

• Provide the applicant's external ID in the Applicant ID parameter. Nexla automatically pages through the transition history.

List Applicant Notes

List all notes recorded on an applicant's profile.

• Provide the applicant's external ID in the Applicant ID parameter to retrieve that applicant's notes.

List Openings (Funnels)

List all openings (recruiting funnels/positions) available to the account.

• This endpoint returns paginated results. Nexla automatically pages through all openings on the account.

Get Opening

Retrieve a single opening (funnel) by ID.

• Provide the opening's external ID in the Opening ID parameter to fetch that specific opening.

List Opening Stages

Retrieve the ordered list of hiring stages for an opening.

• Provide the opening's external ID in the Opening ID parameter whose stages you want to list.

Get Stage

Retrieve a single hiring stage by ID.

• Provide the stage's external ID in the Stage ID parameter to fetch that specific stage.

List Positions

List all positions defined on the account.

Get Position

Retrieve a single position by ID.

• Provide the position's external ID in the Position ID parameter to fetch that specific position.

List Locations

List all hiring locations configured on the account.

• This endpoint returns paginated results. Nexla automatically pages through all configured locations.

List Users

List all account users (Fountain admins/recruiters) with name, ID, and email.

List Workers (Partners)

List all workers (hired/active partner records) on the account.

• This endpoint returns paginated results. Nexla automatically pages through all worker records.

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

Fountain data sources can also be manually configured to ingest data from any valid Fountain 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.

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 Fountain 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Fountain destination, and select the Send to Destination option from the menu. Select the Fountain connector from the list of available destination connectors, then select the credential that will be used to connect to Fountain, and click Next; or, create a new Fountain credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Fountain endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Applicant

Create a new applicant on a given opening.

• Each record from your Nexset is sent as a JSON request body to create a new applicant. Ensure the record contains the applicant fields required by the Fountain API, including the target opening.

Update Applicant

Update an existing applicant's profile fields.

• Provide the applicant's external ID in the Applicant ID parameter. Each record is sent as a JSON request body containing the fields to update.

Advance Applicant (Move Stage)

Move an applicant to the next stage, or to a specific destination stage/funnel.

• Provide the applicant's external ID in the Applicant ID parameter. Include the destination stage or funnel in the record body to move the applicant to a specific stage rather than the next one.

Create Applicant Note

Add a note to an applicant's profile.

• Provide the applicant's external ID in the Applicant ID parameter. Each record is sent as a JSON request body containing the note content.

Manual configuration

Fountain destinations can also be manually configured to send data to any valid Fountain API endpoint. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Fountain APIs expect JSON format for write operations. For update operations, include the ID of the applicant to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Fountain endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Fountain endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.