Invite a candidate to a Codility test and retrieve session results via the Codility API
domain: codility.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register your application in the Codility developer portal to obtain an API access token; record the HTTP header format required for authentication.
Identify the numeric test ID from your Codility account for the test you wish to send.
POST to the invite endpoint (path pattern: /api/tests/{test_id}/invite/) with the candidate email and any optional parameters such as candidate name or expiry duration.
Store the returned session identifier which will be needed to retrieve results later.
After the candidate submits, GET the session results using the session ID from the /api/sessions endpoint to retrieve score, task results, and code submissions.
Write the result data back to your ATS candidate record, including the direct link to the Codility report for recruiter review.
Known gotchas
The API access token is per-application and scoped to your account; rotating or regenerating it invalidates all existing integrations that depend on the old token.
Session results may not be immediately available after a candidate finishes — build a polling delay or use webhook notifications if supported for your plan tier.
Codility's API documentation notes that endpoint paths and response schemas can change between API versions; pin to a documented version and monitor release notes.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?