Skip to main content
Welcome to the Proview SDK (v8). Follow these steps to embed the latest SDK in your application.

Prerequisites

  • Talview-provisioned tenant + project DSN. You get a separate DSN per environment (dev / staging / prod).
  • Ability to add a script tag and a small bootstrap snippet wherever proctoring needs to run.

Content Security Policy (CSP)

If your application enforces CSP headers, apply the policy in Getting Started → Content Security Policy. It is the same for every Proview module.

1. Load the SDK once

Proctoring uses the same loader as every other Proview module. Add it once, as the last script on any page that needs proctoring, following Getting Started → Installation. The loader attaches itself globally as window.Proview and fires window.proviewOnLoad when ready.
Use the environment-specific loader URL shared during onboarding (dev / staging / prod). The example above targets the production CDN.

2. Initialise once per page view

Initialisation has two calls, both made inside window.proviewOnLoad:
  1. Proview.init({ dsn }) bootstraps the SDK. The session module loads by default, so you do not need a modules array. See Getting Started → Initialize for the full options.
  2. Proview.session.init({ ... }) registers this proctoring session: its identifier, the attendee and the workflow step.
Options marked // required below must be supplied in session.init; Proview.session.start no longer accepts them. See the init options for every field.
workflow_step.flow_uuid (optional) is the proctoring configuration identifier for the provided dsn. Please note: if the workflow step is already created with a flow, this will not override it.

Host checklist

  • Set dsn once, on Proview.init. It is applied to the session automatically and cannot be overridden in session.init.
  • Provide attendee (with identifier), workflow_step (with identifier), and a top-level identifier — all required — during session.init.
  • Check each identifier against the rules in the init options.
  • Do not gate your own UI on the loader script—wait for the session to enter the MONITORING_IN_PROGRESS state (next section).

3. Start the proctoring session before showing the assessment

Trigger the session start from your own UI (for example, a “Start Exam” button) once the candidate is ready. Wait for the promise to resolve before displaying your assessment content.

4. Stop, complete, pause, and resume

The session module mirrors the methods listed in Interfaces:
All operations update the local session context and invoke your onError handler on failure. When rolling out pause/resume, consider mapping them to your own assessment timers as well.

Next steps

  • Playback — replay a recorded session in your reviewer-facing app
  • Troubleshooting — loading, init, auth, and permission failures
  • Best Practices — guidance that applies to every module