Greenhouse Harvest v3 Migration Guide

Last updated: June 9, 2026

Greenhouse is moving all integrations to the more secure Harvest API v3, which uses OAuth 2.0. To ensure uninterrupted access to the HackerRank–Greenhouse integration, you will need to connect your Greenhouse account to the Harvest v3 API before August 28, 2026.

HackerRank understands that changes to integrations can require additional effort from recruiting and admin teams, especially when they affect critical hiring workflows. HackerRank is working closely with Greenhouse to make this transition as smooth as possible and to support customers through each step of the migration.

Migrating to Harvest v3

This migration is a two-part process: first, you complete the one-time Harvest v3 connection in HackerRank; then, HackerRank Support will migrate your integration to the new v3 API and deprecate the existing API connection on your behalf.

Step 1: Complete the one-time Harvest v3 connection in HackerRank

This step establishes the new Harvest v3 connection and allows HackerRank to verify that your account is ready for migration.

  1. Log in to your HackerRank account using your company admin credentials.

  2. Go to Settings > Integrations > Greenhouse > Connect, or open the Greenhouse integration page directly.

  3. In the Connect to Greenhouse Harvest v3 API section, click Connect.

    connect.png

  4. Log in to your Greenhouse account as prompted. Once you are logged in to Greenhouse, you will be redirected to HackerRank to complete the authorization process.

    GH-Step-4.png

  5. Review the permissions requested by HackerRank and click Authorize.

    GH-Step-5.png

    After you complete the authorization, a confirmation page appears displaying the status Connected.

  6. Click Close tab to return to the Greenhouse integration page in HackerRank.

    2026-06-04_04-12-48.png

  7. Verify that the Connect to Greenhouse Harvest v3 API section displays Connected.

    2026-06-04_03-57-45.png

You do not need to update your existing Harvest API token, Greenhouse User ID, or any other fields in the existing Greenhouse API details section. These fields will remain unchanged during this step.

Step 2: HackerRank completes the migration

After your Harvest v3 connection is completed and verified, HackerRank will migrate your integration on the backend within the following 2–3 weeks. You do not need to take any additional action for the backend migration.

HackerRank will migrate customers in batches during a weekly migration window on Fridays from 3:00–4:00 PM Pacific Time.

After migration, the HackerRank team will validate that your integration is working as expected and send you a confirmation email once your migration is complete.

Frequently Asked Questions (FAQs)

The FAQs below answer common questions about the Greenhouse Harvest v3 API migration.

Why do I need to migrate?

Greenhouse will deprecate Harvest API v1 and v2 on August 31, 2026. After that date, integrations that continue to use those versions will no longer function. HackerRank will proactively reach out to migrate all affected customers before the deprecation.

Does this change affect both tests and interviews?

Yes. A single OAuth connection supports both Screen and Interview. You do not need to complete separate setup steps for each product.

Do I need to update the existing Harvest API Token or Greenhouse User ID?

You do not need to update your existing Harvest API Token or Greenhouse User ID.
The only action required is to complete the one-time OAuth connection from the Greenhouse integration settings page in HackerRank. This connection prepares your account for the Harvest v3 migration.
Harvest v3 does not use user impersonation. Instead, Greenhouse attributes integration actions to the Greenhouse user who authorizes the OAuth connection. HackerRank recommends that a Greenhouse administrator or authorized user in your organization completes the authorization.

Can I use Harvest v1/v2 and Harvest v3 simultaneously during the testing period?

HackerRank does not support running Harvest v1/v2 and Harvest v3 simultaneously for the Greenhouse integration. Running both versions simultaneously can create duplicate integration traffic, which may result in duplicate updates or other unexpected behavior in your Greenhouse account.
During the migration and testing period, your existing Harvest v1/v2 API keys will remain available as a rollback option. After HackerRank verifies that your Harvest v3 connection is working correctly, the HackerRank team will complete the backend migration and support you through the transition.

Will there be downtime during the migration?

HackerRank will verify the connections to Greenhouse and perform weekly batch migrations for the customers from Harvest v1/v2 to Harvest v3. The migration window is on Fridays between 3:00 PM and 4:00 PM Pacific Time. During this window, there may be a brief service interruption. The HackerRank Support team is available to help you through the migration process.