Skip to content
Developers & integrations

Plan an LMS or platform integration

Separate backend session creation, frontend proctoring and the return of results.

Guide reviewed:

Three connected parts

Your platform supplies the exam content and participant journey. TrustExam’s documented integration combines backend session creation, a frontend Proctoring SDK and result delivery through reports or webhooks.

Map the flow

  1. Your backend sends the assignment and participant identifiers to TrustExam with the agreed settings.

  2. The response provides external_session.token and report_url.

  3. Your frontend uses the session token to initialise the SDK in the exam page.

  4. The application handles configuration, start, finish, action and error callbacks.

  5. Your backend receives configured webhooks and connects the report to the correct attempt.

Decide before implementation

Agree identity mapping, attempt identifiers, Browser/Desktop/Tray mode, the LMS start point, language, enabled monitoring, storage requirements and human review responsibilities. Keep long-lived API credentials on the backend.

Validate the complete journey

Use an authorised test environment and test participants. Check login, permissions, interrupted sessions, explicit submission, attempt limits and result reconciliation. A successful SDK mount alone does not verify the whole exam flow.

Detailed reference

Use the linked official backend, SDK and reporting articles for the current contract. Confirm deployment-specific endpoints and credentials with the TrustExam technical team.

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.