Skip to main content
Telara

Integrations / Greenhouse

Greenhouse logo

Greenhouse

Greenhouse Recruiting Harvest API for jobs, candidates, applications, users, departments, offices, and hiring workflow review.

OAuth 2.0
Indexes
Actions
Events

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events Yes

Before you connect

Prerequisites

A Greenhouse Harvest API user.
Site admin, or a user who can create Harvest keys.

Vendor setup

Get the credential

1
Open Dev Center
In Greenhouse, go to Configure → Dev Center → API Credential Management.
2
Create a Harvest key
Create a Harvest API key for Telara and copy it.
3
Paste in Telara
Settings → Integrations → Greenhouse. Use the Harvest key as the username. The password can be empty or a placeholder.

Permissions Telara requests

  • harvest:jobs:list
    OAuth 2.0
  • harvest:candidates:list
    OAuth 2.0
  • harvest:applications:list
    OAuth 2.0
  • harvest:users:list
    OAuth 2.0
  • harvest:departments:list
    OAuth 2.0
  • harvest:applications:update
    OAuth 2.0
  • harvest:applications:move
    OAuth 2.0
  • harvest:applications:hire
    OAuth 2.0
  • harvest:applications:reject
    OAuth 2.0
  • harvest:applications:unreject
    OAuth 2.0
  • harvest:candidates:create
    OAuth 2.0
  • harvest:candidates:destroy
    OAuth 2.0
  • harvest:candidates:update
    OAuth 2.0
  • harvest:jobs:update
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

Harvest v3 OAuth, client-credentials grant. The customer creates "Harvest V3 (OAuth)" credentials in Greenhouse (Configure > Dev Center > API Credentials) and grants the scopes above -- self-serve, no partnership required (the authorization-code flow at auth.greenhouse.io/authorize is a separate partner-only path). client_id/client_secret are sent as HTTP Basic; the bearer token returned lives 3600s. All list endpoints require the credential to be authorized by a Site Admin. v1/v2 basic auth was removed 2026-08-31 and is deliberately NOT kept as a fallback -- it cannot work.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Knowledge

What gets indexed

ResourceCoverage
CandidatePartial — not every record the vendor holds is synced
JobPartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
CandidateUp to 1 dayRemoved records disappear on the next full sync
JobUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Candidate, Job.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Ingestion / Job Board keys are the wrong class for this connector.
Harvest access is per credential. A key that cannot see a department will not list those openings.