Obtain your Truework API key from the Truework dashboard and include it in requests as Authorization: Bearer <API_KEY>.
POST to the verifications endpoint with a JSON body containing the subject's details (name, employer, consent confirmation) and the verification type requested (employment, income, or both).
Receive a verification object with an ID and initial status in the response; store the ID for status tracking.
Poll the verification status endpoint using the ID, or configure a webhook to receive status change notifications as the verification progresses.
Once the verification reaches a completed status, retrieve the verification report data from the response object.
Known gotchas
The authorization header format is Authorization: Bearer <token> — not 'Token' or any other scheme; using the wrong scheme returns a 401.
Employment verifications may route through Truework's manual or automated fulfillment paths depending on the employer; completion time varies from near-instant to several business days.
Subject consent must be obtained and confirmed before initiating a verification — Truework requires this for legal compliance and the API will reject requests lacking consent confirmation.
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