Build your Own ATS easily
You already have a hiring product, job board, or recruiter UI. You shouldn't have to rebuild resume parsing, scoring, translation, and recorded interview workflows around it.
Use Curriculo's hiring API to add those capabilities while keeping your own product, records, and interface. One API key covers the hiring tasks your team would otherwise need to build and maintain.
Build vs buy
Building your own ATS makes sense when hiring workflows are part of the product you sell. A job board may need structured candidate records. An HR tool may already own the recruiter experience. A homegrown tracker may need scoring without replacing its existing data model.
In those cases, buy the AI layer and keep the parts that distinguish your product. Curriculo's API handles defined hiring tasks while your application remains the system your users work in.
If your main goal is to run hiring for your own company, maintaining a custom product may add work without improving the process. Curriculo's ATS provides the recruiter interface, pipeline, and careers page.
Use the build-vs-buy guide to choose the path that fits your product and team.
What the API does
-
Resume parsing API
A pile of resumes gives your product documents when it needs candidate records. Manual entry slows recruiters and makes every import depend on someone retyping the same details.
Send resumes through the resume parsing API and receive structured candidate data back. Your product can place that data into its own workflow, search, or recruiter UI.
This is the base layer for teams that want to build their own ATS without building a resume parser first.
-
Resume scoring API
Reviewers need to understand how a candidate relates to a specific role. A generic candidate record doesn't answer that question, and a score without context gives the person making the decision little to work with.
Send resumes with the job through the resume scoring API. The response includes a score and written reasoning, which may cover matched skills, gaps, and summary points.
Your product decides where to display the result. A person still decides who moves forward.
-
Translation
Hiring products often receive text or documents in a language different from the reviewer's working language. Building separate translation handling around each part of the product creates more paths to maintain.
Send text or documents to the API and receive translations back. The translated content can remain inside the candidate record, review screen, or workflow your users already know.
Translation uses the same API key as the other capabilities in Curriculo's hiring API.
-
Interview transcription and summary
Recorded interviews create another review task. Someone needs the transcript and a useful hiring summary before the recording can support a decision.
Send a recording or a transcript through the API and receive a transcript and a hiring summary. Your product can show the result beside the candidate's application and job-match information.
The response supports review. It doesn't make the hiring decision.
-
Screening-interview invites
Scheduling a live conversation for every initial screen can consume recruiter time before the team has enough information to proceed. A one-way recorded screen lets candidates answer defined questions without coordinating calendars.
Your product can send screening-interview invites through the API. Candidates record their answers, and the answers can return as a transcript scored by AI.
This is a one-way recorded screening interview. It isn't a live AI interviewer.
Pricing
The Console API is pay as you go. Your own Console sign-up includes $5 free credit for the first calls, then you add credit as you go.
Console is a separate developer product with its own sign-up. It isn't included in Curriculo Starter or Pro.
Or use ours
If you don't want to build your own ATS, use Curriculo's ATS. It includes editable pipeline stages and stage automations, plus careers pages that can run on a custom domain.
The ATS product also provides API keys and MCP. Starter and Pro are separate from the pay-as-you-go Console API.
Docs
The quickstart, implementation guidance, and technical details live in the API documentation. Follow those instructions when connecting your product rather than treating this page as an integration reference.
FAQ
Is it worth building your own ATS?
It can be worth building your own ATS when hiring workflows are part of your product and you already own the records or recruiter UI. If you only need to run hiring, an existing ATS avoids maintaining another internal system.
What does an ATS API do?
An ATS API adds hiring capabilities to your product through software calls. Curriculo's API can parse resumes, score them against jobs, translate content, produce interview transcripts and summaries, and send screening-interview invites.
How does resume parsing via API work?
You send resumes to the resume parsing API and receive structured candidate data back. Your product can store and present that data without requiring recruiters to retype each resume.
Can I score resumes against a job by API?
Yes. Send resumes with the job to receive a score and written reasoning, while a person remains responsible for deciding who moves forward.
How is the API priced?
The API is pay as you go, with $5 free credit for the first calls. After that credit, you add credit as you go.
Is the API part of Starter or Pro?
No. The API is a separate pay-as-you-go Console product with its own sign-up and $5 free credit.
What can't it do?
It isn't a no-code builder and doesn't add custom fields or white-label your product. You build the product, while the API parses, scores, translates, transcribes and summarizes interviews, and sends screening-interview invites.
Can I run screening interviews through the API?
Yes. The API can send invites for one-way recorded screening interviews, then provide an AI-scored transcript from the candidate's recorded answers. It isn't a live interviewer.