Overview

Begini integrates into your application or onboarding workflow to capture behavioural data, generate a risk score, and return results for decisioning. This article gives you an end-to-end view of how the flow works before you move into technical setup.

The core flow

Every Begini integration follows the same sequence regardless of which path you use:

1. A session is created for a user
2. The user completes the assessment journey
3. Begini processes the behavioural data in real time
4. Results are returned — via Beacon, API, or webhook

Two integration paths

Option 1 — No-code (Link Generator)

The fastest way to get started. Generate assessment links directly from Beacon, distribute them to users via SMS, email, or WhatsApp, and review results in the Beacon dashboard. No development work required.

Best for: pilots, early testing, manual or semi-manual rollout models.

Option 2 — API integration

For production-scale deployments. Create sessions programmatically, embed the assessment directly into your application journey, and receive results in real time via webhooks. This is the standard path once the no-code flow has been validated.

Best for: automated decisioning, scalable live deployments, embedded customer journeys.

Most teams start with Option 1 to validate the assessment flow, then move to Option 2 for production.

Key identifiers

Two identifiers are used in every Begini interaction:

Integration ID — identifies the specific deployment being used. Controls the assessment configuration, scoring setup, and branding. Found in Beacon → Deployment Centre. Each deployment has separate Test and Production Integration IDs.

Unique ID (UID) — identifies the end user in your system. Passed when creating a session and returned with the result, allowing you to match Begini outputs back to the correct record internally. Must be 5–60 alphanumeric characters. Must not contain PII.

See Integration ID & Unique ID Guide for full detail.

How results are delivered

For production deployments, webhooks are the recommended approach. See Webhooks Overview for setup details.

Where Begini sits in your workflow

Begini is typically introduced at the pre-decision stage — during application or onboarding — where it adds behavioural signal alongside your existing credit data. It is not a replacement for your current decisioning framework; it is an additional layer that improves risk separation, particularly for thin-file applicants.

Next steps

• Quick Start Guide — run your first assessment with no code
• Integration ID & Unique ID Guide — understand the key identifiers
• Creating a Session — API session creation reference
• Webhooks Overview — real-time results delivery