Skip to content
Developers & integrations

Embed and control the Proctoring SDK

Initialise the SDK, handle lifecycle events and explicitly finish the attempt.

Guide reviewed:

Initialise with a session token

The official SDK article provides the script URL and the Proctoring.initialize call. Mount it in the intended container and pass the external_session.token returned by your backend. The documented language values are en, ru and kz.

Handle the lifecycle

  1. Use onMounted for SDK mounting and onConfigured for loaded configuration.

  2. Start the attempt with Proctoring.start after the required initialisation flow.

  3. Handle onStarted, onAction and onError so the page shows the actual state rather than assuming success.

  4. Call Proctoring.finish when the participant submits the exam, and handle the returned promise and finish callback.

  5. Offer Proctoring.startNewAttempt only when the assignment allows it. The documented helper methods include isFinished and isCanStartNewAttempt.

ContentProtect configuration

The documented setup combines backend content_protect with the frontend protector object, including a match selector for the protected content. Test it on the actual question layout and delivery mode; do not infer protection of content outside that configured area.

Verify the integration

Check permission denial, a failed start, reconnection and repeated finish actions. Keep the exam’s answer submission and the proctoring attempt state consistent. Refer to the official SDK article for exact code and current method details.

Official instructions

YOUR NEXT STEP

Still need help?

Reach the right team for your question.

A technical problem

For the camera, microphone, app or equipment check, open support chat inside TrustExam when available in your session. If you cannot sign in, use the contact in your invitation.

Open TrustExam

Access, schedule or results

Contact your exam organiser using the details in your invitation. They handle assignment access and timing, grades, retakes, appeals and individual arrangements.

What to check before contacting them
What to include in a support message
  • Exam name and the step where the problem occurred.
  • The time and your time zone.
  • Exact error text, operating system, and browser or app version.
  • Checks already tried; an error screenshot without exam questions or unnecessary personal data.

Do not include passwords, sign-in codes or identity documents in an ordinary message. Use the exam’s designated identity-check step for documents.