--- title: Homerun API Integration on Truto slug: homerun category: ATS canonical: "https://truto.one/integrations/detail/homerun/" --- # Homerun API Integration on Truto **Category:** ATS **Status:** Generally available ## Unified APIs ### Unified ATS API - **Attachments** — The attachments represent an attachment for a candidate. - **Candidates** — The candidates represent a candidate. - **Job Interview Stages** — The job interview stages represent a job interview stage. - **Jobs** — The jobs represent a job. ## How it works 1. **Link your customer's Homerun account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Homerun.** The Proxy API is a 1-to-1 mapping of the Homerun API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Automate AI resume screening for design-forward SMBs** — AI screening SaaS companies can pull new candidates and their attachments from Homerun via Truto's Unified ATS API, run resume evaluations against the job description, and push scored summaries back as notes — so hiring managers on small teams never have to manually sift through unqualified applicants. - **Inject assessment results into Homerun hiring workflows** — Pre-employment assessment platforms can detect candidate stage changes, trigger skill tests automatically, and post grades and playback links directly into Homerun's candidate timeline via notes — filling a gap Homerun intentionally leaves open. - **Syndicate jobs from Homerun to external boards and marketplaces** — Niche job boards and sourcing platforms can sync open vacancies from their customers' Homerun accounts, display them on high-traffic sites, and push applicants back as new candidates with attached portfolios — giving SMBs broader reach without leaving their ATS. - **Enrich candidate profiles from background check or reference platforms** — Background screening SaaS products can read candidate data from Homerun, initiate checks externally, and write verification results and status updates back as notes on the candidate record, keeping hiring managers informed inside the tool they already use. - **Power sourcing extensions that push passive candidates into Homerun pipelines** — Sourcing tools and browser extensions can create new candidates directly in Homerun job pipelines via Truto, attaching resumes and tagging the source — enabling customers to track sourcing ROI without manual data entry. ## What you can build - **Automated candidate ingestion from external sources** — Create new candidates in Homerun job pipelines and attach resumes or portfolios programmatically when applicants apply through your platform. - **Real-time job listing sync** — Pull open vacancies from Homerun including descriptions and metadata to display them on your job board, marketplace, or internal matching engine. - **AI-powered candidate scoring notes** — Evaluate inbound candidates against job requirements and post structured scoring summaries directly into Homerun's collaborative candidate timeline as notes. - **Resume and portfolio attachment uploads** — Upload candidate documents — resumes, portfolios, headshots — to existing Homerun applications so hiring managers have everything in one place. - **Stage-aware workflow triggers** — Poll candidate records to detect interview stage changes and automatically kick off downstream actions like assessments, reference checks, or offer generation. - **Source attribution tracking** — Tag candidates pushed into Homerun with your platform's name as the source, giving mutual customers clear visibility into which channel each applicant came from. ## FAQs ### What authentication method does Homerun use? Homerun's API v2 uses API key authentication. End users generate a key from their Homerun account settings. Truto handles storing and injecting the key so your application never manages raw credentials directly. ### Do my customers' end users need a specific Homerun plan to use the integration? Yes. Homerun's API access is gated behind their top-tier 'Plus' plan (approximately €249/month). End users on lower plans will not be able to generate an API key or use the integration. ### What ATS objects can I access through Truto's Unified ATS API for Homerun? Truto's Unified ATS API maps to Homerun's core objects: Jobs (Homerun calls them Vacancies), Candidates (Job Applications), Attachments (Job Application Files), and Job Interview Stages. Note that Homerun does not expose a standalone interview stages endpoint — stages are properties of the job application. ### Can I write data back to Homerun or is it read-only? You can both read and write. Candidates support GET, POST, and PATCH operations. Attachments support POST for uploading files. Notes can be posted to candidate timelines. Jobs (Vacancies) are read-only via GET. ### How does Truto handle pagination and API quirks for Homerun? Truto abstracts away Homerun's pagination logic, rate limiting, and endpoint naming differences (e.g., Vacancies vs. Jobs) behind the Unified ATS API. You write one integration against the unified schema and Truto handles the Homerun-specific details. ### Are there Homerun-specific tools available through Truto today? Homerun-specific tools are not pre-built but are available on request. The Unified ATS API already covers the core objects — Jobs, Candidates, Attachments, and Job Interview Stages — so most common workflows are supported out of the box.