Apideck integration – Greenhouse Support

Apideck is an integration infrastructure for B2B software. Software companies use Apideck's unified APIs to build and maintain integrations with the platforms their customers run, with 200+ connectors across seven unified API categories including ATS, HRIS, accounting and CRM.

The Greenhouse connector gives your product access to Greenhouse Recruiting through Apideck's unified ATS API. You read jobs and job posts, and read and write candidates, using the same API and data model you already use for every other ATS connector. You enable the connector once in the Apideck Dashboard. Your users then connect their own Greenhouse account through Apideck Vault, which runs the Greenhouse OAuth flow and stores and refreshes the tokens, so your product never handles Greenhouse credentials. This integration is intended for Greenhouse partners.

Requirements

An Apideck account with the ATS Unified API enabled.
Greenhouse OAuth client credentials for the integration - your own Greenhouse-issued partner credentials. Greenhouse requires every integration to authorize with its own credentials.
The Greenhouse user who authorizes a connection must be a Site Admin, or have the "Can manage ALL organization's API credentials" permission (Greenhouse: Connect to Harvest V3 partner integrations).

Configure the Apideck integration

Obtain your Greenhouse OAuth credentials

Request a Client ID and Client Secret for your integration from Greenhouse (via your Greenhouse partnership contact), with the redirect URI registered as https://unify.apideck.com/vault/callback. During authorization, your users see your integration's name and logo on the Greenhouse consent screen.

Enable the connector in the Apideck Dashboard

Go to Configuration > ATS > Greenhouse in the Apideck Dashboard.
Enable the connector for your application.
Enter your Client ID and Client Secret.
Save. The connector is now available to all of your users in Vault.

Apideck Dashboard showing the Greenhouse connector configuration with Client ID and Client Secret fields

Use the Apideck integration

This section covers how you implement Apideck Vault in your product, and how your users authorize their Greenhouse account through it.

Implement Vault in your product

Apideck Vault is the connection manager your users interact with — it presents the Greenhouse connection flow, runs the OAuth authorization, and stores and refreshes the tokens. You never build a Greenhouse-specific auth screen; you surface Vault. There are three ways to do it:

Hosted Vault — the no-code option. Create a Vault session for your user (POST /vault/sessions) and redirect them to the returned session URL. Apideck hosts the connection UI.
Embedded Vault — the same experience inside your own product, using Apideck's Vault component libraries (Vault JS / React). Open Vault in a modal with the session token, optionally deep-linked straight to the Greenhouse connector.
Vault API — build a fully custom UI on the Vault API and drive the connection state yourself.

Whichever route you choose, the Greenhouse OAuth flow, token storage, rotation, and refresh are handled by Vault — your product never sees or stores Greenhouse credentials.

Authorize a Greenhouse connection (your users)

Your user opens Vault from within your product and selects Greenhouse.
They click Authorize and are redirected to Greenhouse (auth.greenhouse.io) to sign in and approve the requested scopes.
Greenhouse requires the authorizing user to be a Site Admin or hold the "Can manage ALL organization's API credentials" permission. Site Admins can alternatively authorize with an organization-level service account — a dedicated identity with no username or password that persists until disconnected, so the connection doesn't break when an individual leaves.
After approval, the user is redirected back to Vault and the connection is active.

Apideck Vault connection screen with Greenhouse selected