Developers

Build on ProofAware.

Use the public REST API to sync people, author courses, launch assignments, and connect your own automation or LLM workflows. ProofAware provides the training and evidence rails; you bring the systems around it.

Base URL
https://web.proofaware.com/api/v1

Authentication
Authorization: Bearer pak_your_api_key

API keys are scoped to one workspace and stored hashed. The live reference is generated from the same validation schemas as the API.

REST API

Author, assign, and sync from your own stack.

The v1 API covers the workflow surface teams usually automate: courses and versions, assignments and enrollments, members, and departments.

Course authoring

Create courses, versions, and modules from your own systems or AI-assisted workflows.

Assignments

Launch campaigns, track enrollments, and cancel assignments through the same API surface.

Members and departments

Sync workspace members and department structure from HR or directory tooling.

OpenAPI first

Generate typed clients or inspect the live reference from the OpenAPI 3.1 document.

Workspace-scoped access

Grant only the scopes a workflow needs. Write scopes imply read access for the same resource, and every request stays inside the workspace that issued the key.

courses:read/writeassignments:read/writemembers:read/writedepartments:read/write
curl -H "Authorization: Bearer pak_your_api_key" \
  https://web.proofaware.com/api/v1/courses
Get an API key

Create keys inside ProofAware.

Workspace owners and admins can create, scope, revoke, and rotate API keys from Settings -> API. Plaintext keys are shown once; store them in your secret manager.

Open API settings
MCP

Agent access is next.

ProofAware's MCP server will let Claude, Cursor, and other MCP clients work with the same API surface for course authoring and training operations. A published package is planned; early adopters can follow the source today.

Coming soonView source