Overview

Begini generates webhook events when there are status updates during the application and scoring journey.

These events allow your system to track progress, receive score outputs and respond to different user outcomes in real time.

Each event type has a specific purpose and payload structure.

---

Event categories

Begini webhook events broadly fall into two groups:

Application journey events

These describe the state of the application process.

Score completion events

These describe when a score has been calculated and is ready for use.

---

psychometric_score.complete

This event is generated when a psychometric score result is available.

It is the main event used when working with the Begini Psychometric Assessment.

Typical contents

• application start and completion times
• score completion time
• platform
• calculated score
• risk band
• score confidence
• trait-level outputs
• flags

When to use it

Use this event when you want to:

• receive the final psychometric score
• process behavioural outputs
• trigger decisioning or review workflows

---

application.complete

This event is generated when the user finishes the application journey.

It confirms completion of the application flow.

Typical contents

• application start time
• application completion time

When to use it

Use this event when you want to:

• track completed journeys
• separate completion from scoring
• trigger operational workflow steps

Note: in the legacy documentation, the example payload appears to show the wrong event type. This should be corrected to application.complete.

---

android_score.complete

This event is generated when a score result is available from an Android device data integration.

Typical contents

• application start and completion times
• score completion time
• platform set to ANDROID
• calculated score
• risk band
• permissions granted
• permissions denied

When to use it

Use this event when integrating Android device data scoring.

---

ios_score.complete

This event is generated when a score result is available from an iOS device data integration.

Typical contents

• application start and completion times
• score completion time
• platform set to IOS
• calculated score
• risk band
• permissions granted
• permissions denied

When to use it

Use this event when integrating iOS device data scoring.

---

application.expired

This event is generated when the user does not complete the application journey within the allowed timeframe.

Typical contents

• application start time
• application expiry time
• percentage completed

When to use it

Use this event when you want to:

• track abandoned journeys
• identify timeouts
• monitor incomplete funnel behaviour

---

application.incomplete

This event is generated when the user submits the application journey without fully completing all required parts.

Examples include:

• unanswered sections
• missing permissions
• incomplete flow steps

Typical contents

• application start time
• last response submission time
• percentage completed
• reasons

When to use it

Use this event when you want to:

• detect partial submissions
• identify missing data
• trigger review or retry processes

---

application.cancelled

This event is generated when the user terminates or does not proceed with the application journey.