RecruspaceParse API
Search⌘K
Try it →
API  /  Response schema

Response schema

The stable parse envelope, and the 24-field candidate object returned by extraction. Fields are only ever added — never removed or renamed.

Parse envelope

FieldTypeDescription
markdownstringFull document in reading order; tables as HTML.
chunksarraySection-level blocks, split on headings.
splitsarrayOne block per page.
metadataobjectfilename, page_count, dpi, duration_ms.
instant_fieldsobjectemails, phones, links, linkedin, github.
candidate_dataobject | nullThe 24-field object below (from extraction).

candidate_data

Scalars are null when absent; lists are [].

FieldType
first_name, last_name, email, phone_numberstring
address, date_of_birth, general_titlestring
summary_cover_letterstring
total_work_experiencenumber
resume_skills, hobbies_interests, driving_license, other_informationarray<string>
work_experience_detailsarray<experience>
education_detailsarray<education>
languagesarray<language>
certifications_conferences_seminars_courses, honors_awardsarray<item>
projects, publications, recommendationsarray<item>
volunteer_extracurricular_activities, examsarray<item>
linksarray<{url}>

Key nested shapes

JSONshapes
work_experience_details[] = {
  company_name, position_title, employment_type,   // full_time|part_time|contract|intern
  start_date, end_date, currently_employed,        // boolean
  position_description, position_keywords
}
education_details[] = {
  school_name, degree,                             // bachelor|master|phd|associate|high_school|other
  major, start_date, end_date, currently_pursuing, // boolean
  grade, description
}
languages[] = { language, proficiency }        // conversational|professional|native_bilingual

Compatibility

The envelope follows a strict additive policy — new fields may appear, but existing fields keep their names and types. Parse defensively and ignore unknown fields.