Reference / Changelog
Changelog
Notable changes to the Parse API. The response envelope is additive — fields are only ever added, never removed or renamed, so integrations keep working.
2026-07-23
- BREAKING — separate artifacts:
/v1/parse-extractand job results/webhooks now return{"parse": {…}, "extract": {…}}— two independent objects to persist separately.candidate_datano longer appears inside the parse envelope;?full=trueremoved. - Job
statussimplified topending → processing → done | failed; webhook delivery runs in the background and never delays the result.
2026-07-22
- New: POST /v1/autofill — form-prefill fast path; fire it in parallel with a parse call. Digital PDFs answered deterministically (<1 s); scanned PDFs via a validated vision pass.
- New: POST /v1/parse-extract — both artifacts (markdown + candidate data) in one response.
- Structured extraction is now ~4× faster (~5–10 s typical) with stricter
verbatim behaviour — values are copied character-exact and unprinted dates return
null. - Sync endpoints now read the first 10 pages (was 3); longer documents are truncated, not rejected.
1.0
POST /v1/parse— synchronous parse. Send afileor asource_url(a pre-signed link); get clean markdown + instant contact fields.POST /v1/extract— structured extraction from parsed markdown into the 24-field candidate object, so a submit step never re-processes the CV.POST /v1/jobs— asynchronous parse with HMAC-signed, retried webhook delivery; the full result is available for 7 days.- Stable response envelope (
markdown/chunks/splits/metadata/instant_fields) and the 24-fieldcandidate_dataschema. - Interactive Try it console served on this domain.
- Turkish-first, diacritic-exact parsing; handles mixed Turkish/English CVs.
Building an integration? Start with the Quickstart and keep this page bookmarked for breaking-change notices (there won't be any that remove or rename a field).