| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Job Visibility filter
Confidential jobsThis endpoint doesn't return applications belonging to confidential jobs by default.
If you want to include applications belonging to confidential jobs add confidential to job_visibility filter (filter[job_visibility]) alongside other visibility options.
Including Structured Section Responses
If you want to include structured section responses in your request, ensure your params include the following: include=structured_section_responses.answers
Attachments
To include application attachments (e.g. CVs) in your response, use the extra_fields parameter:
https://your-subdomain.pinpointhq.com/api/v1/applications/1?extra_fields[applications]=attachmentsThis will return the application with the attachments.
Note: You must scope the extra field under applications:
✅ extra_fields[applications]=attachments
🔴 extra_fields=attachments (wrong)
Parsed CV data (work and education history)
When a candidate's CV is parsed, Pinpoint stores one record per role in their work history and one per qualification. You can read these records alongside the application by including the resume and its histories:
include=resume.employment_histories,resume.education_histories- No extra API key scope is needed. Any key that can read the application can read the parsed CV data.
- These records are read-only, and you can only reach them through this include. There is no separate endpoint for them.
start_dateandend_dateare strings copied from the CV (for example2011-01,2009orcurrent). They are not always valid dates, so don't parse them as dates without checking.- If no CV was parsed,
relationships.resume.dataisnulland the response has no CV records underincluded.
Example response
{
"data": {
"id": "1",
"type": "applications",
"attributes": { "...": "..." },
"relationships": {
"resume": {
"data": { "type": "resumes", "id": "21" }
}
}
},
"included": [
{
"id": "21",
"type": "resumes",
"attributes": {
"created_at": "2026-06-29T16:07:50+00:00",
"updated_at": "2026-06-29T16:07:50+00:00"
},
"relationships": {
"employment_histories": {
"data": [{ "type": "employment_histories", "id": "161" }]
},
"education_histories": {
"data": [{ "type": "education_histories", "id": "1" }]
}
}
},
{
"id": "161",
"type": "employment_histories",
"attributes": {
"employer_name": "Acme Corporation",
"organisation_name": "Acme Corporation",
"title": "Head of Engineering",
"description": "Led the payments team and moved billing onto a new platform.",
"current": true,
"start_date": "2019-03",
"end_date": "current",
"country_code": "GB",
"region": "England",
"municipality": "London",
"job_level": "Executive (VP, Dept Head)",
"skills_category": null,
"skills_comments": null,
"created_at": "2026-06-29T16:07:50+00:00",
"updated_at": "2026-06-29T16:07:50+00:00"
}
},
{
"id": "1",
"type": "education_histories",
"attributes": {
"school_name": "University of Manchester",
"start_date": "2012",
"end_date": "2015",
"city": "Manchester",
"state": null,
"country": "United Kingdom",
"comments": "University of Manchester\nBSc Computer Science, 2012 - 2015",
"created_at": "2026-06-29T16:07:50+00:00",
"updated_at": "2026-06-29T16:07:50+00:00"
}
}
]
}