Docs

Integration workflows

Choose a complete workflow for your recruiting backend.

Start with your first analysis and test it in the developer sandbox. Then add the workflows your product needs.

Integration checklist

Save application references, resource IDs, attempt IDs, and idempotency keys in durable storage. Keep secrets on your backend. Reconcile current state before applying an old webhook. Store result revisions and treat absent evidence as unavailable.

The default report summary stays compact. Request include=reference when you need application references and use a detailed result endpoint for evidence. Newly added API scopes require an appropriately scoped key; subscribe explicitly to the webhook events your receiver handles.

See API concepts for shared semantics and the reference for exact contracts.

On this page