Referral and postback
Applicants move to your branded flow with signed click, source and campaign identifiers. A server-to-server postback returns the agreed application or outcome state for attribution and routing feedback.
Start with a referral and server-to-server postback, or receive structured applications through a direct API. The same routing logic and attribution identifiers carry across both modes.
Applicants move to your branded flow with signed click, source and campaign identifiers. A server-to-server postback returns the agreed application or outcome state for attribution and routing feedback.
Qualified applications are posted as structured JSON using a field map agreed with your team. Idempotency keys, response handling and retry behavior are defined before live traffic begins.
Sample payloads and test credentials let both teams exercise validation, error responses and outcome callbacks. Live routing starts only after the field contract and operational contacts are confirmed.
Share your preferred delivery mode and current system constraints. We will outline the fields, callbacks and test sequence needed for onboarding.