/v1/resumes/parseNormalize resume fields and attach page-level source refs.
Developers can embed source-linked resume intelligence without losing audit fields, scorecard versions, or downstream review state.
curl https://api.cvault.tech/v1/candidates/score \
-H "Authorization: Bearer $CVAULT_API_KEY" \
-d '{
"candidate_id": "cand_789",
"role_id": "role_123",
"include_evidence": true
}'Send parser output, scorecard context, source refs, reviewer state, audit events, and ATS status as one contract your platform team can inspect.
/v1/resumes/parseNormalize resume fields and attach page-level source refs.
/v1/candidates/scoreApply role criteria, knockout flags, and scorecard weights.
/v1/evidence-exportsPackage reviewer state, evidence refs, and ATS status.
/v1/webhooksEmit parse, score, review, export, and delivery events.
/v1/evidence-exportsidempotency-key: export_cand_789_role_123{
"candidate_id": "cand_789",
"role_id": "role_123",
"role_fit": 0.94,
"scorecard_version": "v3.7",
"review_state": "shortlisted",
"ats_status": "synced",
"evidence_refs": 28,
"source_refs": [
"resume.pdf:p2",
"portfolio.pdf:p7"
],
"webhook_event": "export.synced"
}Authentication, rate limits, webhooks, payloads, and SDK access are part of the buyer conversation.
Bearer token and workspace-scoped API access patterns.
Review parse, score, export, and webhook throughput before rollout.
Candidate, evidence, scorecard, review, and export objects.
Public status surface and incident path for production consumers.
Use permitted resumes, one live role, private workspace controls, and exportable evidence before a wider rollout.