Skip to main content

Upgrading to Greenhouse Harvest API V3 in Guide

Guide now supports the Greenhouse Harvest API V3 - upgrade to take advantage

Updated today

To take advantage of Harvest V3 from Greenhouse, your team simply needs to generate a new V3 API key and add it to your existing Guide<>Greenhouse integration tile. Once added, Guide will automatically use your V3 data — no other configuration is required.

✅ Why upgrade?

Greenhouse’s Harvest API V3 offers improvements in structure, performance, and access granularity. While your current integration likely uses a V2 key, V3 ensures compatibility with the latest Greenhouse platform features and is now fully supported by Guide.


🔧 How to create and add your v3 Harvest API key

  1. Log into your Greenhouse Dev Center

    Go to your Greenhouse dashboard and navigate to API Credential Management.

  2. Create a new API key

    • Click Create New API Key

    • Select API Type: Harvest API V3

    • Add a short description (e.g., “Guide Integration V3”)

    • Click Create

  3. Copy the credentials

    • You’ll be given a Client ID and Client Secret

    • Copy both values — you’ll need to paste them into Guide

  4. Paste into Guide’s GH integration tile

    • Head to your Drive settings page in Guide

    • Look for the Harvest V3 integration section

    • Paste in the Client ID and Client Secret, then save

  5. Verify and you’re done

    • Once the credentials are added, Guide will automatically begin using Harvest V3 endpoints behind the scenes.

    • No further setup is required. Existing workflows will continue to function using V3 data.

📝 Notes

  • You can keep your V2 key active during the upgrade — Guide will prioritize the V3 key once detected.

  • If you’re unsure whether your data is flowing via V3, contact Guide support for confirmation.

  • Only one V3 key is needed per organization.


🔒 Required scopes

Please ensure your new Harvest v3 key has the following scopes enabled to ensure full compatibility with Guide:

📌 These scopes should mirror what’s granted to your existing v2 Harvest key.

Did this answer your question?