Homerun API · unofficial, by Cotlet
Create your own Homerun API
Homerun's pricing table marks the Public API on the Plus plan only, and trials are excluded (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Homerun account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Homerun session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Homerun. Homerun is a trademark of its owner. If Homerun's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/waiting-candidates" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"days": 7}' const url = "https://cotlet.dev/api/v1/custom/waiting-candidates";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ days: 7 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/waiting-candidates",
headers={"Authorization": f"Bearer {key}"},
json={"days": 7},
)
data = res.json()["data"] {
"data": [
{
"candidate": "Ana R.",
"job": "Barista",
"stage": "Applied",
"days_waiting": 9
},
{
"candidate": "Raj P.",
"job": "Shift lead",
"stage": "Interview",
"days_waiting": 8
}
]
} 01 Build
How do you build a Homerun endpoint with Cotlet?
-
Sign in to Homerun in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List the candidates who have waited more than 7 days without a reply, with job, stage and days waiting."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a job or a number of days, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Homerun session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Homerun
Cotlet ships no fixed list of Homerun endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/waiting-candidates Candidates waiting for a reply
Candidate, job, stage and days waiting
-
POST
/api/v1/custom/new-applicants New applicants
Applicants per job since the date you name, with their answers
-
POST
/api/v1/custom/stage-counts Pipeline per job
Candidates per stage for each open job
-
POST
/api/v1/custom/candidate-notes Notes on a candidate
Every note on one candidate, newest first
-
POST
/api/v1/custom/writesadd-candidate-note Add a note to a candidate
A note on the candidate you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/waiting-candidates" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"days": 7}' The answer is JSON, with your fields under data:
{
"data": [
{
"candidate": "Ana R.",
"job": "Barista",
"stage": "Applied",
"days_waiting": 9
},
{
"candidate": "Raj P.",
"job": "Shift lead",
"stage": "Interview",
"days_waiting": 8
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Homerun endpoints for?
- Friday Cotlet endpoint Slack or email
A Friday follow-up list.
Candidates waiting more than a week, sent to Slack or email.
- Weekly endpoint Google Sheets
A hiring sheet.
Applicants per job and stage, pulled into Google Sheets every week.
- Daily endpoint Team chat
New applicants in your team chat.
Each morning, yesterday's applicants posted for the hiring team.
- Chat agent endpoint notes
Your own screening assistant.
A chat agent that reads a candidate's notes before it suggests interview questions.
04 Access
What can an endpoint see and change?
An endpoint works in your own Homerun session, so it can read and change only what your Homerun login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as adding a candidate note, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Homerun have an official API?
Homerun has a Public API on the Plus plan, with keys made by admins; it creates and moves candidates, adds notes and tags and reads jobs (checked 20 Nov 2026). Homerun says it does not support setting up integrations with it. The full picture with sources: Does Homerun have an API or MCP server?
Want ChatGPT or Claude to work in Homerun instead of code? See the Homerun MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Homerun API with Cotlet: questions
Is this an official Homerun API?
No. Cotlet is independent and not affiliated with Homerun. The endpoints you build run in your own signed-in Homerun account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Homerun changes its screens?
An endpoint works while Homerun works the way it did when you built it. If Homerun changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Homerun endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.