Obtain an API key and environment URL from ProctorU during the implementation process; include the key in the Authorization-Token header on all requests
Create a user record in ProctorU for the test-taker if one does not already exist, providing name and email; store the returned user identifier for subsequent reservation calls
Create an exam reservation using the appropriate workflow endpoint (addBlueBirdExam or equivalent) specifying the exam window, duration, and the test-taker's user ID; retain the returned reservation identifier
Use the external resources configuration API to specify which materials (notes, calculators, browser tabs) the test-taker is permitted during the exam; this sets the pre-check configuration the proctor sees
After the exam, poll or receive a webhook for the session review status; retrieve the session recording URL and any incident flags from the review result for audit storage
Known gotchas
The API key must be kept server-side; embedding it in client-side code exposes the ability for unauthorized parties to create or cancel reservations on your behalf
ProctorU operates multiple product tiers (Record+, Review+, Live+); the API endpoints and available parameters differ by product tier, so confirm which tier your institution license covers before building integrations
Exam cancellation windows have time-based restrictions; attempting to cancel a reservation within the restricted window via API returns an error and the institution may still be charged for the session
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp