Read applications
Updated
Applications live in Orbit today. Reading them over the API is scoped, not shipped. Sending them is: Receive applications from your own careers page takes an application from your own form and tells you where the Virtual CV is, and nothing more.
What is planned
- Structured applicant records for a role, and a single application by id: the applicant’s structured CV as the Orbit applicant view already shows it, the fit score, and the verification state of each claim.
- Verification is reported honestly. A claim is
verifiedonly when a named person confirmed it,pendingwhile a confirmation is outstanding, andunverifiedotherwise. The API will never present an unverified claim as anything else, and neither should a page that renders one. - Its own consent basis. Candidate data is not job data. Reading it needs a scope of its own, and the terms under which an account may store it outside Orbit are part of the work, not a detail after it.
What you can do today
Everything an applicant does after clicking applyLink, or after your own page sends their application, is visible in Orbit → Applicants, including where they came from.
Over the API, GET /v1/applications/{applicationId} answers for the applications your account sent: whether the application stands, and where the Virtual CV is (processing, staged, claimed, deleted or failed). It never carries the CV, and never the candidate’s name or email. That is a status for the page the candidate is looking at, not the record this page is about.
