Resume Parser
ATS Integration

ATS Resume Parsing That Fills Candidate Profiles

Structured resume data you map to your ATS fields

The problem

Recruiters retype candidate information from resumes into ATS platforms many times a day. It is slow and introduces typos in email addresses, phone numbers, and company names that break later communication.

The solution

Resume Parser returns contact details, links, work experiences, educations, and languages as JSON from one synchronous call to https://api.resumeparser.cc/v1/parse. Your integration maps those fields to your ATS through the ATS's own API (for example the Greenhouse Harvest API or the Lever API). We do not ship ready-made ATS connectors; the mapping is code you own.

How it works

  1. 1

    Candidate submits a resume

    Your backend receives the PDF and sends it to the API as multipart form data in the field "file", with your API key as a Bearer token.

  2. 2

    API returns structured data

    The response contains data (firstName, lastName, emailAddress, phoneNumber, linkedInLink, workExperiences, educations, languages) and usage. Parsing is synchronous and can take up to 60 seconds, so set your HTTP client timeout to at least 60 seconds.

  3. 3

    Map fields to your ATS

    Your integration layer maps the JSON to your ATS field structure and writes it through the ATS API.

  4. 4

    Recruiter reviews a filled profile

    The recruiter checks the pre-filled profile instead of typing it in.

Key benefits

Less manual data entry

Contact details, roles, and education arrive as fields instead of text a recruiter has to copy.

One fixed schema

Every response uses the same documented fields, so you write the mapping once.

Synchronous response

No webhooks or polling. Set your HTTP client timeout to at least 60 seconds; most parses finish in under 30.

Works with any ATS that has an API

The output is plain JSON, so anything that accepts structured data can take it.

Questions

Frequently asked questions

No. The API returns JSON and you write the mapping to your ATS through its API.

No. /v1/parse is synchronous and returns the parsed data in the same response.

Every field is optional, so your integration should check for missing values. There is no confidence score.

PDF only, up to 5 MB, with a text layer. DOCX, DOC, RTF, plain text, and scanned image-only PDFs are not supported. There is no OCR.

Test field mapping with your own resumes

Sign up with your email, get an API key, and use the 50 free parses per month to see the JSON you will map to your ATS.

Get API key