Advanced Analytica Advanced Analytica: IBOM
← All connectors
Greenhouse logo

Source connector

Greenhouse

Set up Greenhouse as a source and move its data into your chosen destination.

Version 1.5.3 certified generally available

Greenhouse

Set up the Greenhouse source connector and find its reference information on this page.

Prerequisites

The connector reads the Greenhouse Harvest v3 API, which supports two authentication methods. You need one of these authentication methods:

  • OAuth (Airbyte Cloud only): a Greenhouse Site Admin must approve the consent flow. Airbyte provides the client ID and client secret.
  • Client Credentials: provide the client ID and client secret for a Harvest V3 (OAuth) custom integration credential created in Greenhouse. You can also provide a Site Admin’s user ID.

Whichever method you choose, the token needs the Harvest v3 scopes for each stream you sync. The Start date and Number of concurrent threads settings are optional.

Setup

Choose an authentication method and prepare it in Greenhouse. Then create the source in Airbyte.

Set up Greenhouse

Choose the method that matches your Airbyte deployment and credential source.

OAuth

OAuth (Authorization Code) authenticates through Airbyte’s registered Greenhouse partner application. You don’t create, request or register your own Greenhouse OAuth application. Greenhouse issues partner credentials only to integration partners, not Greenhouse customers. Airbyte provides the client ID and client secret during the consent flow. This method is available only in Airbyte Cloud because it depends on Airbyte’s partner credentials.

To use OAuth, you need:

  • An Airbyte Cloud workspace.
  • A Greenhouse Site Admin who can approve the consent flow.

Client Credentials

Client Credentials uses a Harvest V3 (OAuth) custom integration credential that you create in Greenhouse. Use it with self-managed Airbyte. You can also use it in Airbyte Cloud instead of Airbyte’s partner application.

To use Client Credentials, you need:

  • Access Configure > Dev Center > API Credential Management in Greenhouse. Click Create new API credentials, select Harvest V3 (OAuth) and save the credential. Then grant the scopes listed below. Greenhouse provides a client ID and client secret. Copy both into the source.
  • You can provide the numeric Greenhouse user ID of a Site Admin. Greenhouse creates an integration service user for every custom credential. By default, the connector sends requests as this user, which can read every Harvest v3 list endpoint. Enter a user ID as the Site Admin user ID only to attribute requests to a specific person. Greenhouse denies list endpoints to users who aren’t Site Admins.

Scopes

Both methods need the same scopes. For OAuth, approve every scope requested during the consent flow. For Client Credentials, grant these scopes to the Greenhouse credential:

  • harvest:application_stages:list
  • harvest:applications:list
  • harvest:applied_candidate_tags:list
  • harvest:approval_flows:list
  • harvest:approver_groups:list
  • harvest:approvers:list
  • harvest:attachments:list
  • harvest:candidate_attribute_types:list
  • harvest:candidate_educations:list
  • harvest:candidate_employments:list
  • harvest:candidate_tags:list
  • harvest:candidates:list
  • harvest:close_reasons:list
  • harvest:custom_field_options:list
  • harvest:custom_fields:list
  • harvest:demographic_answer_options:list
  • harvest:demographic_answers:list
  • harvest:demographic_question_sets:list
  • harvest:demographic_questions:list
  • harvest:departments:list
  • harvest:eeoc:list
  • harvest:email_templates:list
  • harvest:interview_kits:list
  • harvest:interviewer_tags:list
  • harvest:interviewers:list
  • harvest:interviews:list
  • harvest:job_candidate_attributes:list
  • harvest:job_hiring_managers:list
  • harvest:job_interview_stages:list
  • harvest:job_interviews:list
  • harvest:job_notes:list
  • harvest:job_owners:list
  • harvest:job_post_locations:list
  • harvest:job_posts:list
  • harvest:jobs:list
  • harvest:notes:list
  • harvest:offers:list
  • harvest:offices:list
  • harvest:openings:list
  • harvest:prospect_details:list
  • harvest:prospect_pool_stages:list
  • harvest:prospect_pools:list
  • harvest:referrers:list
  • harvest:rejection_details:list
  • harvest:rejection_reasons:list
  • harvest:scorecard_candidate_attributes:list
  • harvest:scorecard_question_answer_options:list
  • harvest:scorecard_question_answers:list
  • harvest:scorecard_question_options:list
  • harvest:scorecard_questions:list
  • harvest:scorecards:list
  • harvest:sources:list
  • harvest:user_emails:list
  • harvest:user_job_permissions:list
  • harvest:user_roles:list
  • harvest:users:list

Harvest v3 rejects list endpoint requests from users who aren’t Site Admins or custom integration service users. The connector then stops the sync with a configuration error. A missing scope causes the same failure for dependent streams. Grant every listed scope unless you plan to disable its corresponding streams. Always grant harvest:users:list. The connection check reads the users stream, so setup fails without this scope, even if you never sync it.

With OAuth, Greenhouse links scopes to the refresh token issued when you approved consent. Versions 1.2.0, 1.4.0, and 1.5.0 each added streams requiring new scopes. Tokens created before one of these versions don’t include its added scopes. Enabling streams added in 1.2.0, streams added in 1.4.0, or streams added in 1.5.0 then causes a 403 error. Open the source settings, click Authenticate and approve consent again. Existing synced streams keep working without re-authentication. The consent flow requests scopes for the source’s current version. Re-authenticate after an upgrade, not before. Connections that propagate all field and stream changes enable new streams automatically. Syncs then fail with a 403 until you re-authenticate or disable those streams. With Client Credentials, grant the new scopes to the Greenhouse credential instead.

Set up the connector in Airbyte

  1. Log into your Airbyte Cloud account or open your self-managed Airbyte instance.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Greenhouse from the Source type dropdown.
  4. Enter a name for the Greenhouse connector.
  5. Under Authentication, select OAuth or Client Credentials.
    • For OAuth (Airbyte Cloud only), click Authenticate. Sign in to Greenhouse as a Site Admin and approve the requested scopes. Airbyte enters its partner application’s client ID and client secret, then stores the resulting refresh token. You don’t enter any Greenhouse credentials.
    • For Client Credentials, enter the custom integration credential’s Client ID and Client secret. Leave Site Admin user ID blank to send requests as the credential’s integration service user. Enter it only to send requests as a specific Site Admin.
  6. You can enter a Start date in UTC using the format YYYY-MM-DDTHH:MM:SSZ. Records updated before this date won’t be replicated. If you omit it, the connector replicates all history.
  7. You can change Number of concurrent threads. The connector uses 2 threads by default and accepts 1 to 8. All threads share one Greenhouse rate limit. Increase this only if your Greenhouse account can handle more API traffic. Reduce it to 1 if syncs fail with rate-limit errors.
  8. Click Set up source.

:::warning If you use OAuth, sync at least once every 14 days. Greenhouse refresh tokens expire after 14 days of non-use and rotate on every refresh. If a connection pauses, stops or fails for over 14 days, repeat consent from the source settings. See Sync fails with a configuration error asking you to re-authenticate for the resulting error. Client Credentials has no refresh token, so this doesn’t apply. :::

Supported sync modes

The Greenhouse source connector supports these sync modes:

Start date filters the Greenhouse request, not the sync. Every incremental stream listed below sends updated_at=gte|<start date> with each sync. This includes streams configured as Full refresh. A full refresh therefore returns only records updated on or after your start date. Leave Start date empty to replicate all history.

Incremental streams reread a one-hour window before the saved cursor during each sync. This captures records updated shortly before the previous sync finished. Incremental - Append can therefore create duplicate destination records. Use Incremental - Append + Deduped, where supported, to keep only each record’s latest version.

Supported streams

New connections enable 10 streams by default: applications, candidates, jobs, job_posts, offers, interviews, scorecards, users, departments, and offices. Enable other streams from the connection’s stream list.

The table shows each Airbyte stream name and its Harvest v3 endpoint. Start date applies to every stream marked incremental, regardless of its selected sync mode. It doesn’t apply to other streams. Only the four demographics question and answer-option streams use full refresh. Harvest v3 provides no date filter on /v3/demographic_questions or /v3/demographic_answer_options, so these streams always read every returned record. Their two child streams retrieve parent IDs across your full Greenhouse history. Their coverage therefore doesn’t depend on Start date.

StreamSync modeNotes
activity_feedIncremental (updated_at)Notes across all candidates
application_stagesIncremental (updated_at)Stage history per application, with time in stage. One row per application per stage entered
applicationsIncremental (updated_at)
applied_candidate_tagsIncremental (updated_at)Candidate-to-tag assignments; tags on its own is only the dictionary
approvalsIncremental (updated_at)
approver_groupsIncremental (updated_at)The steps of an approval chain, per approval flow
approversIncremental (updated_at)Individual approvers and their status within a group
attachmentsIncremental (updated_at)One file per application. url is a download link Greenhouse expires after seven days
candidate_attribute_typesIncremental (updated_at)The scorecard attribute dictionary, defined per job
candidate_educationsIncremental (updated_at)School, degree and discipline history per candidate
candidate_employmentsIncremental (updated_at)Employer and title history per candidate
candidatesIncremental (updated_at)
close_reasonsIncremental (updated_at)
custom_field_optionsIncremental (updated_at)Every custom field option in the account
custom_fieldsIncremental (updated_at)
degreesIncremental (updated_at)Custom field options for the degree field
demographics_answer_optionsFull refresh
demographics_answersIncremental (updated_at)
demographics_answers_answer_optionsFull refreshAnswer options for each question in demographics_questions
demographics_question_setsIncremental (updated_at)
demographics_question_sets_questionsFull refreshQuestions in each set in demographics_question_sets
demographics_questionsFull refresh
departmentsIncremental (updated_at)
disciplinesIncremental (updated_at)Custom field options for the discipline field
eeocIncremental (submitted_at)
email_templatesIncremental (updated_at)
interview_kitsIncremental (updated_at)Kit content per job interview. exercises is the live value and may contain HTML
interviewer_tagsIncremental (updated_at)The interviewer tag dictionary
interviewersIncremental (updated_at)One row per panel member on a scheduled interview
interviewsIncremental (updated_at)
job_candidate_attributesIncremental (updated_at)The scorecard attributes rated on each job. scorecard_candidate_attributes.job_candidate_attribute_id references this stream
job_hiring_managersIncremental (updated_at)One row per hiring manager on a job
job_interviewsIncremental (updated_at)The interview plan for each job stage
job_notesIncremental (updated_at)Free-text notes on jobs, separate from the candidate notes in activity_feed
job_ownersIncremental (updated_at)Recruiter, sourcer and coordinator per job, with a responsible flag
job_post_locationsIncremental (updated_at)One row per location attached to a job post, published or not, resolved to an office, a custom location or free text
job_postsIncremental (updated_at)Includes deleted posts
job_stagesIncremental (updated_at)
jobsIncremental (updated_at)
jobs_openingsIncremental (updated_at)Openings across all jobs
offersIncremental (updated_at)
officesIncremental (updated_at)
prospect_detailsIncremental (updated_at)Pool, stage and owner per prospect application
prospect_pool_stagesIncremental (updated_at)The stage dictionary for each prospect pool
prospect_poolsIncremental (updated_at)
referrersIncremental (updated_at)Referral attribution per candidate
rejection_detailsIncremental (updated_at)Reason, rejecter and note per rejected application
rejection_reasonsIncremental (updated_at)Includes the reasons Greenhouse ships with
schoolsIncremental (updated_at)Custom field options for the school_name field
scorecard_candidate_attributesIncremental (updated_at)One row per rated attribute on each scorecard
scorecard_question_answer_optionsIncremental (updated_at)The options picked on each single_select or multi_select answer
scorecard_question_answersIncremental (updated_at)Interviewers’ answers to scorecard questions. One row per question on each scorecard, including questions left blank
scorecard_question_optionsIncremental (updated_at)The choices for single_select and multi_select scorecard questions
scorecard_questionsIncremental (updated_at)The question dictionary behind scorecards, defined per interview kit
scorecardsIncremental (updated_at)
sourcesIncremental (updated_at)
tagsIncremental (updated_at)Candidate tags
user_emailsIncremental (updated_at)Every email address per user; users.primary_email is only one of them
user_permissionsIncremental (updated_at)Job permissions across all users
user_rolesIncremental (updated_at)
usersIncremental (updated_at)Includes integration service users

Streams added in 1.5.0

Version 1.5.0 added these 5 streams, all incremental on updated_at. Together with scorecard_questions, the scorecard streams include each scorecard’s content, not just its overall recommendation. job_candidate_attributes names the attributes rated by scorecard_candidate_attributes:

job_candidate_attributes, job_post_locations, scorecard_question_answer_options, scorecard_question_answers, scorecard_question_options

All 5 are disabled by default on new and existing connections. Each needs its own Harvest v3 scope. If you authorised an OAuth source before 1.5.0, repeat consent after upgrading and before enabling these streams. Connections propagating all field and stream changes enable all five when 1.5.0 arrives. Syncs then fail with a 403 configuration error until you repeat consent or disable the streams. To prevent this, select propagation of field changes only before upgrading. With Client Credentials, grant harvest:job_candidate_attributes:list, harvest:job_post_locations:list, harvest:scorecard_question_answer_options:list, harvest:scorecard_question_answers:list, and harvest:scorecard_question_options:list to the Greenhouse credential. See Scopes.

Streams added in 1.4.0

Version 1.4.0 added these 2 streams, both incremental on updated_at:

candidate_attribute_types, job_notes

Both streams are disabled by default on new and existing connections. However, Airbyte enables them during upgrades when the connection propagates all field and stream changes. Each stream needs its own Harvest v3 scope. For OAuth sources authorised before 1.4.0, repeat consent before enabling either stream. With Client Credentials, grant harvest:candidate_attribute_types:list and harvest:job_notes:list to the Greenhouse credential. See Scopes.

Streams added in 1.2.0

Version 1.2.0 added these 20 streams, all incremental on updated_at. They contain details embedded in Harvest v1 parent records but served through separate Harvest v3 endpoints:

application_stages, applied_candidate_tags, approver_groups, approvers, attachments, candidate_educations, candidate_employments, interview_kits, interviewer_tags, interviewers, job_hiring_managers, job_interviews, job_owners, prospect_details, prospect_pool_stages, referrers, rejection_details, scorecard_candidate_attributes, scorecard_questions, user_emails

All 20 streams are disabled by default on new and existing connections. However, Airbyte enables them during upgrades when the connection propagates all field and stream changes. Each stream needs its own Harvest v3 scope. For OAuth sources authorised before 1.2.0, repeat consent before enabling any stream. With Client Credentials, grant the corresponding scopes to the Greenhouse credential. See Scopes.

Streams made incremental in 1.1.0

These 18 streams used full refresh before 1.1.0. They are now incremental on updated_at:

activity_feed, approvals, close_reasons, custom_field_options, custom_fields, degrees, demographics_question_sets, departments, disciplines, jobs_openings, offices, prospect_pools, rejection_reasons, schools, sources, tags, user_permissions, user_roles

This isn’t a breaking change. Schemas, primary keys and existing sync modes remain unchanged. There was no stream state to migrate, so you don’t need to act. Connections continue syncing.

One behaviour changes: Start date now applies to these 18 streams in every sync mode. Earlier versions sent no date filter and read your full Greenhouse history, regardless of Start date. With a start date, these streams now return only records updated on or after it. This applies to full refresh and incremental syncs because Greenhouse filters the request. On a Full refresh | Overwrite connection, this also removes older rows from the destination table. Each sync replaces the table with the records it reads. Existing rows remain on append and append + deduped connections, but stop refreshing. Clear Start date to continue reading full history, then refresh the streams.

Migrate from Harvest v1

Version 1.0.0 moves the 33 streams from 0.8.1 from Harvest v1 to Harvest v3. It also adds the new custom_field_options stream, bringing the total to 34. Greenhouse has scheduled Harvest v1 and v2 support to end together on 2026-08-31. Version 1.0.0 also replaces API-key authentication with OAuth Authorization Code authentication. It introduces an optional Start date that preserves full-history behaviour when omitted. Version 1.3.0 added Client Credentials for self-managed deployments that can’t use OAuth consent. These deployments can authenticate with a credential you create in Greenhouse. Create a new connection on 1.0.0 instead of refreshing the existing one. See the upgrade paths before upgrading.

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Performance

Greenhouse rate limits Harvest v3 in fixed 30-second windows. Each response shows the remaining allowance in X-RateLimit-Remaining. It shows the current window’s reset time in X-RateLimit-Reset. Greenhouse doesn’t publish a fixed Harvest v3 request ceiling. It also gives custom and partner integrations different allowances. The connector therefore limits itself to a conservative 50 requests per window and tracks these headers. When Greenhouse returns 429, the connector waits for the Retry-After interval. Every thread uses the same window. Syncing many streams with a high Number of concurrent threads commonly causes rate-limit errors. Lower this value before creating an issue about rate limits.

The connector requests 500 records per page, the Harvest v3 maximum. It then follows Greenhouse’s cursor links. Large accounts can still require many requests for each stream.

application_stages, scorecard_candidate_attributes, and scorecard_question_answers are high-volume streams. application_stages contains one row for each application and stage entered. scorecard_candidate_attributes contains one row for every rated attribute on each scorecard. scorecard_question_answers contains one row for every question on each scorecard. Each stream contains several times more rows than its parent. They add many requests and consume the shared rate-limit window. Leave them disabled unless you need this detail.

Limitations and troubleshooting

Limitations

  • eeoc replicates on submitted_at. Correcting an EEOC response after submission doesn’t change submitted_at, so incremental syncs don’t reread it. Refresh the stream to replicate corrections.
  • custom_field_options reads every custom field option in your account. It is therefore a superset of degrees, disciplines, and schools. Those three streams read the same Greenhouse endpoint, filtered to one field key. They also share the same primary keys. Enabling all four writes identical option rows to four destination tables. Enable only the streams you need.
  • users includes integration service users, which Greenhouse hides by default. Service accounts have no email address, so primary_email is empty for these records.
  • rejection_reasons includes Greenhouse’s default reasons, not only those added by your organisation.
  • attachments returns a url for each file, which Greenhouse expires after seven days. Each request can redirect to a new short-lived file URL. A replicated url stops working one week after the sync that wrote it. Resync the stream to get current links.
  • application_stages contains one row for each application and stage entered. It therefore holds several times more rows than applications. Enable it only for funnel or time-in-stage analysis.
  • candidate_educations references schools, degrees and disciplines by custom field option ID: school_name_custom_field_option_id, degree_custom_field_option_id, and discipline_custom_field_option_id. Join schools, degrees, and disciplines to resolve their names.
  • interviewers contains one row for each panel member and interview. An interview appears once for every attendee. user_id is empty for external attendees who don’t match a Greenhouse user. Their address appears in email instead.
  • scorecard_candidate_attributes contains one row for each rated attribute and scorecard. It therefore holds many more rows than scorecards.
  • scorecard_question_answers contains one row for each question and scorecard, including unanswered questions. It therefore holds many more rows than scorecards. The question’s answer_type determines which field contains the answer. Use answer for text, boolean_value for yes_no, and scorecard_question_answer_options for single_select and multi_select. value stores every answer as text. This can be the text itself, "true"/"false", an option ID or a JSON array of option IDs such as "[26384455003, 26384458003]". For an unanswered question, answer is empty and value is null. For multi_select, it is "[]".
  • interview_kits.exercises contains the live Interview Prep content and can include HTML. The summary and instructions fields on job_interviews are snapshots from when the slot was first added. They don’t reflect later edits. Use exercises for the current text.
  • user_emails lists every address for a user, while users.primary_email contains one. Integration service users have no addresses, so they have no rows here.
  • approvers.send_auto_reminder_at is a date (YYYY-MM-DD), not a timestamp. This differs from every other Harvest v3 field using the _at timestamp suffix.
  • The 18 streams that became incremental in 1.1.0 now honour Start date. Previously, they always read full history. See Streams that became incremental in 1.1.0.

Deletions

Greenhouse Harvest v3 doesn’t report permanently deleted records. The connector replicates soft deletions using a flag on each record:

  • active on job_posts. Harvest v3 excludes deleted posts by default, so the connector requests active and deleted posts. Filter on active downstream if you only need live posts.
  • active on custom_fields, custom_field_options, degrees, disciplines, schools, demographics_question_sets, demographics_questions, demographics_question_sets_questions, demographics_answer_options, demographics_answers_answer_options, prospect_pools, scorecard_question_options, and job_candidate_attributes. Harvest v3 returns active and inactive records for these streams.
  • deactivated on users. Deactivated users remain in the stream.
  • active on job_stages, job_interviews, and scorecard_questions. false means the stage, interview or question was removed from the job’s interview plan or interview kit. Greenhouse retains the record so historical data still resolves.

Permanently deleted Greenhouse records remain in your destination until you resync the stream in Full Refresh - Overwrite.

Configuration error requests re-authentication

This section applies to OAuth. For Client Credentials, see Client Credentials authentication fails.

The connector can’t renew its access token because Greenhouse rejected the refresh token. From version 1.0.1, this appears as a configuration error instead of a system error. Use the Greenhouse error code in the sync log to identify the fix:

  • invalid_grant: the refresh token expired or became invalid. This happens when the connection hasn’t synced for over 14 days. It also happens when another tool uses the same refresh token. A sync interrupted immediately after token renewal can cause it too. In the last two cases, Greenhouse issued a new refresh token that Airbyte didn’t save. Greenhouse replaces the refresh token during every renewal. Open the source settings, click Authenticate and complete consent again to store a new token. Run consent separately for every Airbyte source. Don’t reuse a refresh token across sources or other tools.
  • invalid_client or unauthorized_client: Greenhouse rejected Airbyte’s partner application credentials during refresh. The application might also lack permission to use the refresh token grant. Open the source settings, click Authenticate and complete consent again. If the error continues, contact Airbyte support. You don’t have any credentials to correct.

Client Credentials authentication fails

With Client Credentials, the connector requests a new Greenhouse access token using your client ID and secret. There is no refresh token to renew. The shared OAuth message still says the refresh token was rejected and asks you to re-authenticate. Use the Greenhouse error code at the message’s end instead:

  • invalid_client: Greenhouse doesn’t recognise the client ID and client secret. Check both against the credential in Configure > Dev Center > API Credential Management. Confirm that the credential hasn’t been revoked.
  • invalid_grant: the Site Admin user ID doesn’t match a Greenhouse user. Correct it or leave it blank. A blank value sends requests as the credential’s integration service user.

Stream fails with a 403 configuration error

The authorising user isn’t a Site Admin, or consent didn’t include the stream’s scope. This is expected when streams added in 1.2.0, streams added in 1.4.0, or streams added in 1.5.0 is enabled on a source authorised before that version. You might have enabled it manually. Airbyte might also enable it during upgrades when the connection propagates all field and stream changes. Compare the scopes with your approved scopes. Then open the source settings, click Authenticate and repeat consent as a Site Admin. With Client Credentials, grant the missing scope to the Greenhouse credential. Confirm that Site Admin user ID is blank or belongs to a Site Admin.

Fewer records after upgrading to 1.1.0

Version 1.1.0 made 18 streams incremental on updated_at. Every sync mode now applies Start date as a Greenhouse query filter for these streams. With a start date, records last updated before it aren’t returned. This applies to incremental and full refresh syncs. If the connection writes in Full refresh | Overwrite, the first post-upgrade sync also deletes older destination rows. Your warehouse therefore shows the gap even though the sync succeeded. Earlier versions didn’t filter these streams by date and ignored Start date entirely. Streams that became incremental in 1.1.0 lists the affected streams.

To read full history again, clear Start date in the source settings. Then refresh the affected streams to write the older records again.

Changelog

Expand to review
VersionDatePull RequestSubject
1.5.32026-10-1388668Update dependencies
1.5.22026-10-0587672Promote the connector to certified
1.5.12026-10-0587670Update to source-declarative-manifest 7.33.0 and name the fix for each authentication method in the 403 error message
1.5.02026-10-0287442Add the scorecard_question_answers, scorecard_question_options, scorecard_question_answer_options, job_candidate_attributes, and job_post_locations streams, which need new scopes - see Streams added in 1.5.0
1.4.02026-09-2886478Add the candidate_attribute_types and job_notes streams, which need new scopes - see Streams added in 1.4.0
1.3.02026-09-2485178Add client-credentials authentication for Greenhouse custom integrations and self-managed deployments.
1.2.02026-09-2186477Add 20 Harvest v3 detail streams, which need new scopes - see Streams added in 1.2.0
1.1.02026-09-1785841Sync 18 previously full-refresh streams incrementally, so Start date now applies to them in every sync mode, and suggest 10 streams for new connections - see Streams that became incremental in 1.1.0
1.0.32026-09-1585507Update dependencies
1.0.22026-09-0285306Clarify in the spec that OAuth credentials come from Airbyte’s Greenhouse partner application and must not be requested from Greenhouse
1.0.12026-09-0285300Surface expired or rotated refresh tokens (invalid_grant) as a re-authenticate config error instead of a system error
1.0.02026-08-2884846Breaking migration from Harvest v1 to Harvest v3 with OAuth. See the migration guide.
0.8.12026-08-1884641Update dependencies
0.8.02026-08-1283811Send pagination page-size parameters only on first-page requests and use fully-qualified per-stream URLs in preparation for the Harvest v3 migration.
0.7.332026-08-1183956Update dependencies
0.7.322026-07-2883194Update to CDK 7.23.8 (fixes AirbyteCustomCodeNotPermittedError for bundled custom components) and remove the temporary Cloud version override
0.7.312026-07-281082Roll Cloud back to 0.7.29 — 0.7.30 is built on SDM 7.23.7, which breaks bundled custom components
0.7.302026-07-2882944Update dependencies
0.7.292026-07-2182444Update dependencies
0.7.282026-07-1481887Update dependencies
0.7.272026-06-3081129Update dependencies
0.7.262026-06-2380487Update dependencies
0.7.252026-06-1679888Update dependencies
0.7.242026-06-0979354Update dependencies
0.7.232026-06-0278766Update dependencies
0.7.222026-05-1578119Set the default concurrency to 2 and expose the number of concurrent threads as a user-configurable option.
0.7.22-rc.32026-05-1278052Reduce default_concurrency to 3 for concurrency tuning after rate-limit failures at higher settings.
0.7.22-rc.22026-05-0878006Concurrency tuning iteration: bump default_concurrency to 5
0.7.22-rc.12026-05-0677826Start concurrency tuning at default_concurrency=4 (Path A) and enable progressive rollout
0.7.212026-04-2877287Update dependencies
0.7.202026-04-2176637Update dependencies
0.7.192026-03-3175729Update dependencies
0.7.182026-03-1774919Update dependencies
0.7.172026-03-1074688Update dependencies
0.7.162026-03-0374176Update dependencies
0.7.152026-02-1073107Update dependencies
0.7.142026-02-0372661Update dependencies
0.7.132026-01-2071894Update dependencies
0.7.122026-01-1471700Update dependencies
0.7.112025-12-1870503Update dependencies
0.7.102025-11-2570056Update dependencies
0.7.92025-11-1869420Update dependencies
0.7.82025-10-2968823Update dependencies
0.7.72025-10-2168226Update dependencies
0.7.62025-10-1467896Update dependencies
0.7.52025-10-0767399Update dependencies
0.7.42025-09-3066408Update dependencies
0.7.32025-09-0965896Update dependencies
0.7.22025-08-2864973Update dependencies
0.7.12025-08-2665510Fix custom migrations to reference DeclarativeStream Pydantic model instead of runtime component
0.7.02025-07-0762830Promoting release candidate 0.7.0-rc.1 to a main version.
0.7.0-rc.12025-06-2947283Migrate to Manifest-only
0.6.12025-03-2253800Update dependencies
0.6.02025-03-1455774Promoting release candidate 0.6.0-rc.1 to a main version.
0.6.0-rc.12025-03-1454702Update to latest airbyte-cdk, remove custom cursors.
0.5.322025-02-0152724Update dependencies
0.5.312025-01-2551842Update dependencies
0.5.302025-01-1151214Update dependencies
0.5.292024-12-2850632Update dependencies
0.5.282024-12-2150109Update dependencies
0.5.272024-12-1449248Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64
0.5.262024-12-1248996Update dependencies
0.5.252024-10-2947110Update dependencies
0.5.242024-10-2347306Add ‘job_post_id’ to applications stream scehma
0.5.232024-10-1246828Update dependencies
0.5.222024-10-0546506Update dependencies
0.5.212024-09-2846159Update dependencies
0.5.202024-09-2145834Update dependencies
0.5.192024-09-1745625Change check stream
0.5.182024-09-1445476Update dependencies
0.5.172024-09-0745229Update dependencies
0.5.162024-08-3144755Update dependencies
0.5.152024-08-1744246Update dependencies
0.5.142024-08-1043595Update dependencies
0.5.132024-08-0343160Update dependencies
0.5.122024-07-2742816Update dependencies
0.5.112024-07-2042240Update dependencies
0.5.102024-07-1341787Update dependencies
0.5.92024-07-1041215Update dependencies
0.5.82024-07-1039601Move spec to manifest, fix readme
0.5.72024-07-0640882Update dependencies
0.5.62024-06-2540451Update dependencies
0.5.52024-06-2239968Update dependencies
0.5.42024-06-0639247[autopull] Upgrade base image to v1.2.2
0.5.32024-04-1936640Updating to 0.80.0 CDK
0.5.22024-04-1236640schema descriptions
0.5.12024-03-1235988Unpin CDK version
0.5.02024-02-2035465Per-error reporting and continue sync on stream failures
0.4.52024-02-0935077Manage dependencies with Poetry.
0.4.42023-11-2932397Increase test coverage and migrate to base image
0.4.32023-09-2030648Update candidates.json
0.4.22023-08-0228969Update CDK version
0.4.12023-06-2827773Update following state breaking changes
0.4.02023-04-2625332Add new streams: ActivityFeed, Approvals, Disciplines, Eeoc, EmailTemplates, Offices, ProspectPools, Schools, Tags, UserPermissions, UserRoles
0.3.12023-03-0623231Publish using low-code CDK Beta version
0.3.02022-10-1918154Extend Users stream schema
0.2.112022-09-2717239Always install the latest version of Airbyte CDK
0.2.102022-09-0516338Implement incremental syncs & fix SATs
0.2.92022-08-2215800Bugfix to allow reading sentry.yaml and schemas at runtime
0.2.82022-08-1015344Migrate connector to config-based framework
0.2.72022-04-1511941Correct Schema data type for Applications, Candidates, Scorecards and Users
0.2.62021-11-087607Implement demographics streams support. Update SAT for demographics streams
0.2.52021-09-226377Refactor the connector to use CDK. Implement additional stream support
0.2.42021-09-156238Add identification of accessible streams for API keys with limited permissions
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.