Skip to content
Developers & integrations

Map API proctoring settings

Align environment, recording, identity and fallback settings with the approved programme.

Guide reviewed:

Use the current configuration contract

The integration guide groups parameters under assignment.settings.proctoring_settings. Confirm supported values and defaults for your deployment before sending a configuration copied from an example.

Map the parameter groups

  1. Environment: checks, allowed browser, displays, full-screen mode and focus monitoring.

  2. Camera and screen: separate streaming/record flags from upload flags for the main camera, second camera and screen.

  3. Identity and audio: photo/video identity checks, document verification, noise and speech detection as approved.

  4. Content controls: ContentProtect, clipboard and extensions according to the exam policy.

  5. Failure handling: mobile restrictions, connection timeouts and fallback behaviour.

Check units and dependencies

Some public parameter descriptions use names ending in seconds alongside examples that need unit clarification. Confirm those units with the technical team instead of treating every numeric example as a safe default. Features can also depend on the selected application mode or compatible hardware.

Validate what actually happens

Use a pilot to compare the sent configuration, participant checks and resulting recordings/reports. Test failure of a required channel. Enable fallback only as an explicit programme decision, and document which monitoring may be absent when it is used.

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.