Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mavera.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Pull data from Greenhouse Harvest API (Candidates, Applications, Job Posts, Scorecards, Rejections) → analyze with Mavera (Personas, Focus Groups, Mave Agent, Generate) → get persona-validated talent brand insights for recruiting, employer branding, and people-ops teams.
Greenhouse Harvest API — Base URL: https://harvest.greenhouse.io/v1. Auth: HTTP Basic (API key as username, blank password) for v1/v2, or OAuth 2.0 for v3. Rate limits: 50 requests / 10 seconds. Pagination via per_page + page query params or Link header.

​
Prerequisites

1

Greenhouse API key

Create a Harvest API key in Greenhouse → Configure → Dev Center → API Credential Management. Grant Candidates, Applications, Jobs, Scorecards, and Rejection Reasons permissions.
2

Mavera API key

Get your key from Mavera dashboard.
3

Environment variables

export GREENHOUSE_API_KEY="your_greenhouse_harvest_key"
export MAVERA_API_KEY="mvra_live_xxxxx"

​
Jobs

#JobGreenhouse DataMavera SurfaceOutput
1Candidate Pipeline → Employer Brand PersonasCandidates by source/stage/rejectionCustom Personas + Focus GroupsEmployer messaging validation
2Job Posting OptimizationJob postingsFocus Groups (Likert + open-ended)Clarity/appeal/authenticity ratings
3Interview Feedback → Hiring PersonaScorecardsMave AgentSuccess-predicting trait analysis
4Rejection Reason AnalysisRejection dataFocus GroupsBrand perception impact report

​
Rate Limits & Production Notes

Greenhouse EndpointLimitStrategy
All Harvest endpoints50 req / 10 sec200ms delay between calls; retry on 429 with Retry-After
Pagination500 per_page maxUse per_page=100 + page param; follow Link header
Scorecards (per application)1 call eachBatch application IDs; cache scorecard results
Greenhouse counts every request against the 50/10s window regardless of endpoint. Scorecard-heavy jobs (Job 3) can hit this quickly when iterating over hundreds of applications. Add a 250ms delay between scorecard fetches or use webhooks for real-time scorecard data.
Checklist:
  • Store GREENHOUSE_API_KEY in a secrets manager — never commit
  • Use HTTP Basic auth: API key as username, empty password (key: → base64)
  • Paginate with per_page + page or follow the Link response header
  • Retry on 429 using the Retry-After header value
  • Monitor Mavera credits at Dashboard
  • For v3 (OAuth 2.0): use the token exchange flow for user-context access

All Integrations

Greenhouse API

Personas

Focus Groups

Mave Agent

Generate