Upgrading Authentication to OAuth

Follow the Authentication instructions to obtain an access token. All requests use https://services.fountain.com; Hire paths start with /api/servicehire/v2/. The token identifies your tenant, so no tenant-specific URL is needed.

This page collects compatibility information for integrations whose configuration still contains a Hire API token or a tenant-specific host.

Replace a Hire API token

If your integration sends X-ACCESS-TOKEN, replace that header with Authorization: Bearer ACCESS_TOKEN, using the access token returned by the OAuth flow. Create the Key and Secret in Profile > Manage API Keys or Settings > Integrations & API Keys; do not enter a Hire API token in the OAuth credentials panel.

Hire private API keys and Trusted Party API Keys are found in Company Settings > Developer Settings > API > Show API Keys. Trusted Party API Keys were limited to creating applicants and shared the private key rate limit. Keep all credentials and requests server-side.

Replace a tenant-specific URL

Configurations may contain https://api.fountain.com/v2/, https://<region>.fountain.com/api/v2/, https://wxp-services.fountain.com, or https://services.<customer_instance>.fountain.com. Replace the host with https://services.fountain.com and use the path shown in the API reference. Hire requests also need the /api/servicehire prefix; other service paths stay as documented.

Primary and secondary Hire API tokens

For integrations that still contain these tokens, Company Settings > API > Show API Keys offers a secondary token, deletion of that token, and promotion of the secondary token to primary. Promotion deletes the primary token.

Changing a token affects every request and webhook service using it. Pause affected traffic before changing it, update each consumer, and resume only after checking its requests. Contact [email protected] for help coordinating a rotation. These controls do not rotate an OAuth client secret or an issued access token.