Obtain API credentials from Certn; authenticate by acquiring a token from the Certn token endpoint and including it as a token authorization header on all requests to https://api.certn.co (production) or https://demo-api.certn.co (development)
List available screening packages via the packages endpoint to identify the package_id for the check type you need (e.g., criminal record, soft check, credit)
Create a new applicant/screening request via the applicants or screenings endpoint with the candidate's name, email, and the selected package_id; the candidate will receive an email to complete their portion of the process
Poll the screening status endpoint using the returned screening ID; Certn enforces a burst rate limit of 120 requests per minute and a sustained limit of 14400 requests per 24 hours — stay within these bounds
When the screening status transitions to complete, retrieve the full result report via the results endpoint; results include component-level pass/fail indicators
Use the development base URL (demo-api.certn.co) for all integration testing; production orders trigger real checks and billing
Known gotchas
Certn's API uses token-based auth, not API key headers; tokens may expire and need to be refreshed — implement token refresh logic from the start rather than storing a single long-lived token
The rate limit of 120 requests per minute is a rolling window; aggressive polling will hit this limit quickly — use webhooks or longer polling intervals where available
Certn serves multiple markets (Canada, US, UK, international); available screening types and result formats differ by jurisdiction — confirm which package IDs are valid for your target region with Certn's support team
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