ATS을 쉽게 만들 수 있습니다.

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.

Curriculo's APIATS을 쉽게 만들 수 있습니다.Your productCurriculo's APIResume parsing APIResume scoring APITranslationInterview transcriptionand summaryScreening-interviewinvites

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Read the API docs

FAQ

ATS 자체를 만드는 것이 가치있나요?

자신의 ATS를 구축하는 것이 가치가있을 수 있습니다. 고용 작업 흐름이 제품의 일부이고 이미 기록 또는 UI 채용자가 소유할 때입니다. 만약 당신이 채용만 해야 한다면, 기존의 ATS는 다른 내부 시스템을 유지하지 않습니다.

ATS API는 뭘 할까요?

ATS API은 소프트웨어 호출을 통해 제품으로 고용 기능을 추가합니다. Curriculo의 API은 자기소개서를 분석하고, 직장에 대한 점수를 부여하고, 내용을 번역하고, 면접 편찬과 요약을 작성하고, 심사 면접 초청을 보낼 수 있습니다.

API를 통해 분석을 재개하는 방법은?

당신은 자기소개서를 API의 자기소개서 분석에 보내서 구조화된 후보 데이터를 받게 됩니다. 여러분의 제품은 채용자가 각 자기소개서를 다시 입력하지 않아도 데이터를 저장하고 제시할 수 있습니다.

API에 취업한 직업에 대해 자기소개서를 기록할 수 있나요?

- 그래요 점수와 적당한 논의를 받기 위해 취업과 함께 자기소개서를 보내십시오.

API의 가격은?

API는 이용시 지불하고, 첫 전화에 5달러의 무료 크레딧이 있습니다. 그 크레딧이 끝나면 크레딧을 더할 수 있습니다.

API는 스타터나 프로의 일부인가요?

아니, 아니 API은 별도의 사용료용 콘솔 제품입니다. 별도의 등록과 5달러 무료 크레딧이 있습니다.

뭘 할 수 없죠?

코드가 없는 빌더가 아니고 사용자 정의 필드를 추가하거나 제품을 화이트 레이블로 표시하지 않습니다. 여러분은 제품을 만들고, API는 분석하고, 점수를 내고, 번역하고, 인터뷰를 복사하고, 요약하고, 시영 인터뷰 초대장을 보내죠.

API에서 심사 인터뷰를 할 수 있나요?

- 그래요 API는 일방적으로 녹음된 심사 인터뷰에 대한 초대를 보낼 수 있으며, 그 후 후보자의 녹음 된 답변에서 AI 점수를 얻은 전록을 제공할 수 있습니다. 이건 생방송 인터뷰가 아닙니다.

ko