Generate a Harvest API key in your Greenhouse account with the necessary permissions for scorecard access.
Note that Greenhouse migrated core endpoints to Harvest v3; verify the base URL and versioning requirements in the current API documentation.
Send GET /v1/applications/YOUR_APPLICATION_ID/scorecards with Basic auth using YOUR_API_KEY as the username and an empty password.
Include the On-Behalf-Of header with YOUR_USER_ID if required by your account configuration.
Iterate over the returned array; each scorecard object contains attributes, ratings, and the interviewer who submitted it.
Handle pagination using the Link header if the application has a large number of scorecards.
Known gotchas
The Harvest v3 migration introduced changes to some endpoint paths and response shapes — consult the current Greenhouse developer documentation rather than relying on older v1-era guides.
The API key is passed as the Basic auth username with an empty password; do not place it in the Authorization header as a Bearer token.
Scorecard access may be restricted by Harvest API key permissions — ensure your key has the appropriate scorecard scope enabled in Greenhouse settings.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp