Parse + Extract

Both artifacts in one call: the raw markdown and the 24-field candidate data arrive in a single response. The simplest backend orchestration.

Equivalent to /v1/parse?full=true, published as an explicit endpoint so your backend stays a simple pair of calls: fire /v1/autofill and /v1/parse-extract in parallel on upload, persist both artifacts from this response, and merge on submit (the candidate's own form edits win over the extracted fields).

Request

Send multipart/form-data — same contract as /v1/parse: file or source_url, max 20 MB, first 10 pages.

Response 200

The full envelope — everything /v1/parse returns, with candidate_data populated:

{
  "markdown": "# Jane Doe\n...",
  "chunks": [ ... ], "splits": [ ... ],
  "metadata": { "filename": "resume.pdf", "duration_ms": 16408 },
  "instant_fields": { ... },
  "candidate_data": {
    "first_name": "Jane", "last_name": "Doe",
    "work_experience_details": [ ... ], "resume_skills": [ ... ]
  }
}

Store markdown and candidate_data server-side; the raw markdown is for your records — never render it to the candidate. All 24 fields: Response schema.

Timing

Typically 10–25 seconds total for a typical CV (parse + extraction in sequence, one round-trip).

Example

curl -X POST "https://prs.recruspace.com/v1/parse-extract" \
  -H "X-API-Key: $KEY" -F "file=@resume.pdf"