greenhouse.io

In Greenhouse, open API Credentials, click Create new API credentials, select Harvest V3 (OAuth), save, and configure the scopes your integration needs, as described in Harvest authentication. Greenhouse then gives you a Client ID and Client Secret. Use them to get a bearer token from https://auth.greenhouse.io/token with the OAuth client-credentials flow.

This is for signed Greenhouse partners. Start with the integration request form, then work with Greenhouse Partner Support as described in the Harvest partner OAuth guide. Provide your integration name, environment, required scopes, redirect URI(s), and logo; Greenhouse issues a Client ID and Client Secret for the authorization-code flow against https://auth.greenhouse.io/authorize and https://auth.greenhouse.io/token.

Create a Harvest API credential in Greenhouse from API Credentials / API Credential Management. The Harvest docs note existing Harvest API credentials can still be used during the v1/v2→v3 transition and for Audit Log token generation; see Harvest authentication and Audit Log authentication. Use the API key as the HTTP Basic username with an empty password (api_key:).

Create a Job Board API credential in Greenhouse API Credentials/API Credential Management. The Job Board API docs state only application submission requires this key. Use the Job Board API key as the HTTP Basic username with an empty password, base64-encoded as api_key:.

For Candidate Ingestion OAuth, provide Greenhouse with your application name, application URL, callback URL, and logo as described in Candidate Ingestion authentication. Greenhouse then supplies a consumer key, consumer secret, token URL, and authorize URL for the OAuth 2.0 flow. Use the resulting bearer access token in API requests.

For Candidate Ingestion basic auth, the customer supplies the partner with a Partner API Key and a service user, per Candidate Ingestion authentication. Use the Partner API key as the HTTP Basic username with an empty password (api_key:), and send the service user's email in the On-Behalf-Of header on every request.

For Candidate Ingestion basic authentication, use the active Greenhouse service user's email address in the On-Behalf-Of header on every request, as required by Candidate Ingestion authentication. This user is typically created specifically for the integration and must be recognized by Greenhouse.

When generating an Audit Log access token, send the Greenhouse user ID in the On-Behalf-Of header, as shown in Audit Log authentication. The request also requires a Harvest API key.