Platform

Connects to what you already run.

Signed webhooks, a REST API and bulk files. No middleware to babysit — and no pretending we have connectors we have not built.

An illustration of the webhook delivery logA schematic of the webhook delivery log: one row per attempt with its trigger, response code and outcome, including a failure that was retried and then replayed. A drawing, not a screen capture.NORTHVALE INSTITUTE OF TECHNOLOGYDashboardReports & analyticsCandidatesQuestion bankAssessment librariesAssessmentsSessionsMonitoringReviewGroupsSettingsWebhooks · delivery logALLFAILEDREPLAYEDTRIGGERRESPONSEOUTCOMECANDIDATE_SUBMITTED200DELIVEREDCANDIDATE_STARTED200DELIVEREDCANDIDATE_ASSIGNED500RETRIEDCANDIDATE_ASSIGNED200REPLAYEDCANDIDATE_REVIEW_COMPLETED200DELIVERED
A delivery that failed, then did not
First attempt500 · RETRIED
Replayed by hand200 · DELIVERED
Event idSTABLE ACROSS BOTH
A RETRY IS SAFE TO PROCESS TWICE
Interface illustration, not a screen capture. Drawn to show the delivery log, including a failure that was retried and then replayed.
How Exam Center connects to your systemsThree routes out of the platform: signed webhooks with seven subscribable triggers, a REST API, and bulk CSV or XLSX import and export.Exam CenterSessionsResultsViolationsDecisionsWebhooks7 signed triggersREST APIScoped by roleBulk filesCSV · XLSXYourstack
01

Seven signed triggers

Candidate assigned, started, submitted, result published, disqualified, review completed, and proctoring violation. Each delivery is HMAC-signed and carries a stable event id, so a retry is safe to process twice.

A signed, replayable webhookSeven triggers, each delivered as a signed, idempotent event with a stable event id, a delivery log, and retry and replay.eventIdtriggerpayloadHMACIDEMPOTENTYOUR API500RETRY7 TRIGGERSEACH SIGNEDASSIGNED · STARTED · SUBMITTED
02

Delivery you can inspect

Editable payload templates with a preview, a test send, a full delivery log, retry and replay.

Every delivery is inspectableEditable payload templates with a preview, a test send, a full delivery log, retry and replay.Delivery logCANDIDATE_SUBMITTED · 200DELIVEREDCANDIDATE_STARTED · 200DELIVEREDCANDIDATE_ASSIGNED · 500RETRIEDCANDIDATE_ASSIGNED · 200REPLAYEDPREVIEW · TEST SEND · RETRY · REPLAY
03

What we do not claim

There are no pre-built CRM, ATS, LMS or ERP connectors today. If someone tells you otherwise, ask to see it. What exists is the API, the webhooks and the file paths above.

What we do not claimThere are no pre-built CRM, ATS, LMS or ERP connectors today. What exists is the API, the webhooks and bulk files.Not builtCRM CONNECTORATS CONNECTORLMS CONNECTORBuiltSEVEN WEBHOOKSREST APICSV AND XLSXASK ANY VENDOR TO SHOW YOU THE LEFT COLUMN
01

API keys for machine access

Scoped API keys let a CRM or ATS call the platform without a human session. A key is shown once, stored only as a hash, and can be revoked. Sessions can carry your own correlation payload, which is echoed back on every webhook so a delivery maps to the record it came from. Available per account — ask us to enable it.

02

API and bulk files

A REST API scoped by the same roles as the console, plus CSV and XLSX import and export for candidates in and results out at batch size.

Bring one paper. We'll run it live.

Thirty minutes, your own exam, no slide deck.