Structured payloads
Candidate fields, score context, gaps, and source hints are designed for downstream review.
For developers
Build parser and evidence workflows with contracts your team can inspect.
CVault developer surfaces prioritize scoped keys, predictable JSON, webhooks, and review-safe evidence payloads.
How can a developer connect CVault without losing review and evidence context?
POST
/api/portal/parse_cv_batch_parallel{
"candidate": "review-safe payload",
"evidence": ["source snippet", "confidence"],
"event": "parse.completed"
CVault fieldATS fieldreview_statuscandidate.noteevidence_refsattachment.meta
Developer primitives
Signed events
Webhook deliveries are intended for server-side verification before workflow mutation.
Backend-first integration
Keep API keys server-side and treat browser calls as app UI, not integration infrastructure.
x-api-key: cv_live_your_key_here
Authorization: Bearer cv_live_your_key_hereReviewed rollout
Keep the first integration small.
Connect one endpoint group, verify output with real reviewers, then expand.