Every candidate, one structured pipeline.
Replace the pile of emails, LinkedIn messages, and ATS notifications with typed channels that capture role, comp, and context upfront.
A recruiting inbox on HMU API captures role, compensation, and context on /hire, purpose and time on /meet, and screening questions on /ask. Candidates cannot submit a blank 'checking in' email. You review structured cards, not attachments named resume-final-v7.pdf. The job: Fill reqs without reconstructing context from email threads.
Your channels
Today vs HMU API
Today
Candidates email a generic jobs@ address with a resume attachedWith HMU API
/hire captures company, role, compensation, and description, structured from the startToday
You schedule screening calls over 4 back-and-forth emailsWith HMU API
/meet includes purpose, duration, and preferred date, one submission, one decisionToday
A hiring manager forwards a LinkedIn thread with no level or compWith HMU API
Incomplete /hire submissions fail validation. You only see cards with the fields you asked for.Required fields by channel
/hire Roles, inbound interest, and referrals /meet Screens and debriefs /ask Process questions without a new email chain How it works
- 01
Sign up (free)
Get your own page at
hmuapi.com/you - 02
Share your link
Put it on your site, LinkedIn, bio, or business card
- 03
Messages arrive sorted
AI scores priority, verifies senders, and routes to the right channel
Make the req the form
Most recruiting inbound is a PDF and a hope. /hire asks for company, role, compensation, and a description before the card exists. You stop opening attachments named final-final to learn the level. Sourcers and job boards that already POST JSON can submit the same schema.
Schedule once
/meet carries purpose, duration, and a preferred date. Screening calls stop taking four emails. If the candidate cannot name the role, they cannot book the screen. That is cheaper than a no-show.
Pipe into the ATS. Do not replace it.
HMU API is the intake. Greenhouse, Ashby, and Lever stay the record. A Zap or webhook can create the candidate when a /hire card clears your bar. Recruiters keep the tools they already report on.
FAQ for Recruiters & HR
Does this replace my ATS?
No. It sits in front of it. Qualified /hire messages can push to Greenhouse, Ashby, or Lever through Zapier or a webhook. The ATS stays the system of record.
How do candidates submit without knowing what an API is?
They don't need to. Each channel is a form. The API is there for job boards, sourcers, and agents that already speak HTTP.
Can I require compensation on every inbound role?
Yes. /hire fields are required at submit time. No 'comp DOE' blanks unless you choose to make that field optional on your page.
What about existing inbound on LinkedIn?
Put the HMU API link in your LinkedIn featured section and email signature. New inbound lands structured. Old threads stay where they are.