Developers

Connect proctoring to your system in a few calls.

Invite candidates, pull sessions and events, and subscribe to events with the REST API. LTI 1.3 for LMSs, a platform integration for your own exam engine, and no-code Zapier, Make and n8n.

For privacy, this animation was created with AI and shows no real people. Try the system yourself →

What you can build

Six ways to connect

REST API

Candidate invites and data

Invite candidates; pull exams, sessions and events; manage event subscriptions (REST Hooks).

LTI 1.3 Advantage

LMS

Dynamic Registration with Moodle 4.1+, Sakai 23+, Canvas and D2L: paste the registration URL and the two systems trust each other. The integrity score appears next to the grade as information; it does not change the grade, and the institution decides.

Platform integration

Your own exam engine

Your platform runs the exam and QProctor only proctors it; the result comes back to you in a signed notification.

Webhook

Result notification

When each session ends, the candidate ID and a risk summary are posted to your URL as signed JSON.

No-code

Zapier, Make, n8n

Subscribe to session started, session finished, high risk, raise hand and activation events without writing code.

xAPI

Learning record store (LRS)

Events are sent to your LRS as xAPI statements: attempted, completed, flagged, asked, registered.

Quick start

Try the connection

One call with a Bearer key

Create a key in the panel under Settings › API; the key is shown only once, when it is created. Test the connection with /ben (“me”). When you invite a candidate (POST /adaylar), the response returns the candidate’s invitation link.

  • Key validity: 30, 90, 180 or 365 days, or no expiry
  • A call without the right scope returns 403; an expired key returns 401
  • A key with the invite scope also sends the invited candidate an email
curl https://YOUR-PANEL-HOST/api/v1/ben \
  -H "Authorization: Bearer qp_YOUR_KEY"
Connection test. Fields and sample JSON for every endpoint are on the API screen in the panel.
REST API · /api/v1

Endpoints and scopes

Each key gets its own scopes; grant only what it needs.

EndpointScopeWhat it does
GET /ben—Connection test (“me”)
GET /sinavlaroku (read)List exams
GET /oturumlaroturum_oku (read sessions)Sessions and results (personal data)
GET /olaylar/{event}/ornekoku (read)Sample JSON for an event type
POST /kancalarkanca (hook)Subscribe to an event (REST Hooks)
DELETE /kancalarkanca (hook)Remove a subscription
POST /adaylaraday_davet (invite)Invite a candidate and get the invitation link
Notification security

Signed, with guaranteed delivery

Result webhook
HMAC-SHA256 signature in the X-Proctor-Signature header; Python and Node.js verification samples in the panel
Webhook retries
Up to 3 retries if your endpoint does not return 2xx; deduplicate by session_id
Platform notification
x-ai-zaman (timestamp) and x-ai-imza (HMAC-SHA256 signature) headers
Platform retries
If unreachable, retried after 1 min, 5 min, 15 min, 1 h, 6 h and 24 h, plus a fallback polling endpoint
LTI parameters
exam_url, proctoring (ai | canli = live | canli_ai = live + AI | kayit = record), sure_dk (duration in minutes), dis_kimlik (external ID) and per-activity proctoring settings
Event codes
62 event types; the report, webhooks and the API use the same codes and risk weights

Create your key and make your first call today

Open a free account, create a key under Settings › API and test the connection. 14-day free trial with 20 candidates.

Start free