Dev, Our CV Parser Just Got Unreasonably Good
Mar 7, 2026
We quietly shipped something big. The SharpAPI CV / Resume Parser endpoint now extracts a significantly wider range of structured fields from candidate resumes - and we think you're going to like it.
New fields now available:
| Field | What you get |
|---|---|
candidate_linkedin / github / twitter / website |
Full social & web profile URLs |
candidate_nationality |
Nationality of the candidate |
candidate_date_of_birth |
DOB in YYYY-MM-DD format |
candidate_summary_objective |
Candidate's own objective statement from the CV |
work_authorization |
Visa or work permit status |
years_of_experience |
Total years derived from positions (integer) |
approximate_age |
Age if determinable from CV data |
brief_summary |
AI-generated professional summary of the candidate |
drivers_licenses |
License types (e.g. B, C) |
interests_hobbies |
Because culture fit is real |
projects |
Project name, description, URL |
volunteer_experience |
Role, org, dates, details |
publications |
Title, publisher, date, URL |
references |
Name, position, company, contact |
That's not just a CV parser anymore, Dev. That's basically a background check with better manners.
|
If you're having trouble clicking the button, copy and paste the URL below
into your web browser:
https://sharpapi.com/en/catalog/ai/hr-tech/resume-cv-parsing |
Why This Actually Matters (Part 2)
If you're building any kind of hiring tool, ATS integration, talent platform, or candidate screening workflow — this update saves you a painful amount of custom parsing logic.
Instead of writing regex to hunt down GitHub URLs or manually calculating years of experience from a wall of text, you get clean, structured JSON back. Every time. For any CV format.
The brief_summary field alone is worth it — an AI-generated professional snapshot of the candidate, ready to drop straight into your UI without any additional processing.
And yes, interests_hobbies is in there too. Because sometimes "competitive chess player" tells you more about a candidate than their third bullet point about being "a team player."
One more thing, Dev — we want your feedback on this. Are there fields you're still not getting that would make your integration cleaner? Edge cases where the parser surprised you (in a bad way)? Hit reply and let us know. This endpoint evolves based on what real developers actually need, and you qualify.
Talk soon, Dawid