API Reference

Use this page to find where each route an agent calls lives. The Agent Platform account routes are listed here; content work links to the Content API reference. Terms such as workspace, classroom, and Content key are defined in Terms.

Where each route lives

Content work goes to the Content API, under /v1/content/classrooms/{classroomId}, with a tf_content_ key. {classroomId} is the defaultClassroomId your account returns. The Content API reference lists every route with its scope and success answer, and links its OpenAPI 3.1 description.

The content routes under /v1/platform were removed on 2026-10-16. See Removed content routes.

Authentication

Send a key as Authorization: Bearer <key>. The account routes take a live Content key (tf_content_) with full access, like the one registration and the dashboard issue. A test key gets 403 platform_content_key_too_narrow. A legacy key (tf_platform_) also works on the account routes, and on nothing else. See Authentication.

Agent Platform routes

Paths are under /v1/platform.

Discovery

Agent self-service

See Agent Self-Service API for bodies and answers.

LTI 1.3

See LTI Registrations, LTI Launch Flow, and LTI Grade Sync.

Health

MCP

See MCP Integration.

Dashboard and internal routes

The Agent Platform dashboard uses its own routes, signed in with a TutorFlow session, to manage workspaces, keys, members, usage, and billing. They do not take API keys and are not part of the public API.

Errors

Agent Platform routes answer errors as:

{
  "error": {
    "code": "platform_invalid_api_key",
    "message": "Invalid or missing Platform API key",
    "error": "Unauthorized",
    "statusCode": 401,
    "status": 401
  }
}

Read code and status. error and statusCode repeat the HTTP status in another form.

Content API routes use content_* codes and add requestId. See Error Handling.

Three answers an agent must handle on every route it calls:

Removed content routes

These Agent Platform routes were removed on 2026-10-16, together with their edit-token and share-token routes and the token editors. Every method on them answers 410, with any key or none:

{
  "error": {
    "code": "platform_route_removed",
    "message": "This Agent Platform content route was removed. Use the Content API with a tf_content_ key: https://tutorflow.io/agent-platform/docs/guides/content-api-migration",
    "migrationGuide": "https://tutorflow.io/agent-platform/docs/guides/content-api-migration",
    "status": 410
  }
}

Do not retry. Call the Content API instead, with a tf_content_ key:

Every route, one by one, is in Migrating to the Content API.