The Boring Project

The job application API. You get the webhook.

The Boring Project is a job application API. Send a job URL and a candidate profile; we complete the employer's form in Workday, Greenhouse, Lever and 40+ other ATSs, file it, and send you the receipt.

40+ ATSsAbout 3 minutes medianConsent on every application

Looking for a job yourself? You want auto apply on jobs, from $99 a year.

Applications, last runFiling
Example applications with ATS, elapsed time and status
ATSRoleTimeStatus
GreenhouseSenior Backend EngineerSenior Backend EngineerNorthwind48sSubmitted
WorkdayStaff AccountantStaff AccountantHalcyon Health6m 31sSubmitted
LeverProduct DesignerProduct DesignerLumen Labs52sSubmitted
iCIMSRegistered Nurse, ICURegistered Nurse, ICURiverbend Medical3m 34sNeeds inputLicense state?
AshbyGrowth MarketerGrowth MarketerPico37sSubmitted
SmartRecruitersField Sales ManagerField Sales ManagerOrion Logistics2m 08sSubmitted
TaleoData AnalystData AnalystMeridian Bank5m 02sFailedPosting closed
RipplingFrontend EngineerFrontend EngineerFinch44sSubmitted
WorkdayClinical Research AssociateClinical Research AssociateAlder Bio1m 37sFilling fields
6 submitted1 needs input1 failedScreenshot receipt attached to each
job application api
How a job application API turns one request into a filed application.

One request in. One filed application out.

The whole apply to jobs API surface. The job URL tells us which ATS to drive; the candidate profile tells us what to type.

RequestPOST /api/v1/sessions/apply
{
  "candidateProfileId": "prof_xyz789",
  "jobs": [{
    "companyName": "Acme Corp",
    "title": "Senior Software Engineer",
    "link": "https://boards.greenhouse.io/acme/jobs/12345"
  }]
}
Webhookapplication.resolved
{
  "sessionId": "sess_abc123",
  "ats": "greenhouse",
  "status": "submitted",   // or needs_input, failed
  "elapsedSeconds": 48,
  "receipt": "https://…/confirmation.png"
}

Every application resolves. Submitted, needs input, or failed, with a screenshot of the confirmation page attached.

Nothing is guessed. A screening question we cannot answer from the profile pauses the run and asks you, once.

How it works

Four steps between your request and a filed application, in order.

01

You send the request

One call with the job posting URL and a candidate object: contact details, work history, resume file and answers to the common screeners.

02

We identify the ATS

The URL resolves to the system behind it, Workday, Greenhouse, Lever or 40+ others, and the matching form adapter loads.

03

The form gets filled

Every field mapped, resume uploaded, screening questions answered from candidate data. Anything we cannot answer truthfully pauses for your input.

04

You get the webhook

Submitted, needs input or failed, with a screenshot receipt of the confirmation page. Your product decides what the candidate sees.

Three ways to use it

Pick by what you already have. All three run on the same apply pipeline and return the same receipts.

You haveJob URLs, candidate profiles and engineers to integrate

Apply API

The core primitive. POST a job URL and a candidate object; receive a submitted application. Built for job-search products that already know where to apply.

  • REST, JSON in, webhook out
  • 40+ ATSs, one schema
  • Screening question engine
Get an API keyPer-application pricing
You haveCandidates, but no job feed

Search + Apply

Job discovery bundled with submission. Query open roles by title, location and ATS, then apply through the same pipeline. One integration, both halves.

  • Structured job feed
  • Dedup and freshness checks
  • Same apply pipeline
Read the docsPer-application pricing
You haveApplication volume and no engineers to spare

Managed Applies

Send us a spreadsheet, get back confirmations. We run the API on your behalf: no integration, no infrastructure, a human review queue on the edge cases.

  • CSV in, receipts out
  • Human review queue
  • No code required
Talk to salesFor agencies and career services

Against building it yourself, or a browser bot

Three ways to build an apply to jobs API capability, side by side.

CriterionThe Boring ProjectBuild in-houseBrowser RPA or scrapers
Time to first applicationUnder an hour3 to 6 months per ATS familyDays, per site
ATS coverage40+ systems, one schemaWhatever you buildPer-site scripts
When forms changeOur problem; adapters monitored around the clockYour problemBreaks constantly, silently
Screening questionsAnswered from candidate data; pauses if unsureYou build the logicUsually skipped or guessed
Proof of submissionWebhook plus screenshot receiptIf you build itRarely
Cost modelPer applicationTwo or three engineers, indefinitelyCheap until it breaks
apply to jobs api
Buying the pipeline against building it, on the costs that appear after the first integration.

Is your ATS covered?

The systems we drive today. Each one has its own adapter and runs a synthetic test application every day.

WorkdayGreenhouseLeveriCIMSTaleoSuccessFactorsSmartRecruitersAshbyWorkableRipplingJobviteBambooHRBreezy HRJazzHRUKG ProADPPaylocityDayforceOracle RecruitingPhenomEightfoldRecruiteePersonioTeamtailorPinpointand 15 more

Missing one? Send the job URL to sales and it becomes our backlog, not yours. Per-system guides: Workday and every other ATS we cover.

The parts that are hard

Applying to jobs by API sounds simple. It is not. Here is what breaks and what we do about it.

Workday is a labyrinth

Multi-step, tenant-specific, often requires creating an account per employer. Our Workday adapter handles account provisioning and step detection per tenant. Median submit time is longer here, and we publish it rather than hide it.

Screening questions have stakes

"Are you willing to relocate?" is a decision, not a field. Anything not answerable from the candidate profile returns needs_input instead of a guess. Fabricated answers get candidates rejected and get APIs banned. We do neither.

Forms change without notice

ATS vendors ship UI changes weekly. Every adapter runs a synthetic test application daily; a failed canary pages us before it fails you. Breakage windows go on the status page, not into your error logs.

Rate limits protect everyone

Employers do not want a flood, and candidates do not benefit from one. We pace per employer and require candidate consent on every application. That keeps the pipes open for everybody, including you.

Questions, answered first

What is a job application API?

A job application API is a web service that submits job applications programmatically. You send a POST request with a job posting URL and candidate data; the API completes the employer's ATS form, including the resume upload and screening questions, submits it, and returns a confirmation webhook with a screenshot receipt.

Which applicant tracking systems are supported?

More than 40, including Workday, Greenhouse, Lever, iCIMS, Taleo, SuccessFactors, SmartRecruiters, Ashby and Workable. If a job you send us resolves to a system we do not cover yet, it goes on our backlog, and unsupported systems are typically added within days.

Is applying through an API allowed?

Yes, when it is a real candidate, with their consent, using accurate data. That is our terms of service, not a loophole. We require consent per application, never fabricate answers and enforce per-employer rate limits. We automate the paperwork, not the honesty.

How fast is a submission?

The median is about three minutes. Single-page systems such as Greenhouse, Lever and Ashby usually finish in under a minute; multi-step enterprise systems such as Workday take longer. Every request resolves to a webhook with a screenshot receipt.

What happens when the form asks something we cannot answer?

The application pauses and you receive a needs_input webhook with the exact question. Answer it once and the run resumes. We never guess at screening questions, because fabricated answers get candidates rejected and get APIs banned.

Who is this for?

Teams building job-search products and teams that move candidates at volume: auto-apply tools, career copilots, staffing agencies, job boards, reverse recruiters and university career services. Your users and your interface; our paperwork.

Applying to jobs is boring. Ship the interesting part.

Your product is the matching, the coaching, the experience. The form-filling is ours. File your first application today.