Webhooks
User APIs do not emit standalone user webhooks in this documentation.
After a user is redirected to Jodo, their actions are reflected through product-specific webhook events. For example, a user may complete Flex setup, make a Pay payment, or progress through a Cred application.
Relevant Webhook Groups
Section titled “Relevant Webhook Groups”- Flex Webhooks: setup, activation, debit, settlement, bounce, cancellation, and closure events.
- Pay Webhooks: student-linked payment debit and settlement events.
- Cred Webhooks: loan application lifecycle events.
- Pay Webhooks: student-linked payment, checkout order, and payment link events.
Implementation Guidance
Section titled “Implementation Guidance”- Store the user
registration_idreturned by Register User. - Store the generated access token only for the redirect session; do not treat it as a long-lived credential.
- Map user activity back to student or product records using IDs in product webhook payloads.
- Follow Webhook Integration for retry, idempotency, and verification guidance.