Guide will handling your transition to Greenhouse's new Harvest API with as minimal disruption as possible, and most of the transition will happen in the background without action needed from you.
Here's how to plan for the transition.
What's happening?
Greenhouse plans to deprecate their Harvest V1/V2 API on August 31, 2026. As of September 1, 2026, your Guide instance will no longer utilize V1 or V2, and will solely depend on Harvest V3 going forward.
Do not remove or revoke your V1/V2 Harvest API key in Greenhouse. To avoid any unexpected service interruptions, Guide will rely on your old keys as a backup until the deprecation date of August 31st, 2026.
What you need to do before August 31st, 2026
Step 1: Head to the Integrations Page in your Guide settings
Click "Update available" under the Greenhouse integration tile.
Step 2: Authorize the Guide app on the required permissions screen
Make sure you are logged in to Greenhouse.
[Recommended] Select the checkbox next to Authorize using a service account. This creates an org-level service account to own the authorization, so the integration keeps working if the authorizing employee later leaves the organization.
Click Authorize.
That's it!
Reminder: Do not remove or revoke your V1/V2 Harvest API key in Greenhouse until August 31st. Guide will rely on your old keys as a backup until the deprecation date of August 31st, 2026 to ensure there are no service interruptions.
Now that your Harvest V3 API key is connected, Guide will handle the transition to Greenhouse's API seamlessly in the background without any service interruption, and you can deprecate your old Harvest API key any time after August 31st, 2026.