Migrating from the Platform content routes

After this guide an integration built on the removed /v1/platform content routes works again on the Content API. New accounts can skip this page.

The content routes of the Agent Platform were removed on 2026-10-16. A call to one now answers 410 with the code platform_route_removed and a link to this page. Courses, modules, tests, slides, videos, games, evaluations, and the learner model live on the Content API, under /v1/content/classrooms/{classroomId}/..., and take a tf_content_ key. The Agent Platform stays as the account layer.

This page lists every removed route with its Content API replacement and what changes in the answer. The full Content API reference is at Content API Reference.

What was removed

• Every route under /v1/platform/videos, /v1/platform/slides, /v1/platform/courses, /v1/platform/tests, /v1/platform/modules, /v1/platform/games, /v1/platform/evaluations, and /v1/platform/learners, including the edit-token and share-token routes.
• The public token editors those routes opened (editToken, previewUrl).
• The webhook endpoint routes under /v1/platform/webhooks.

The content you made on those routes was copied into your account's classroom. Find it with the Content API list routes, such as GET /v1/content/classrooms/{classroomId}/courses.

What stayed

• /v1/platform/agent/*: register, account, billing, x402, email verification.
• /v1/platform/health.
• /v1/platform/pricing-catalog and /v1/platform/.well-known/agent.json.
• The Agent Platform dashboard.
• LTI registrations (/v1/platform/lti/registrations) and the LTI launch routes. See LTI Integration.
• The MCP server at https://mcp.tutorflow.io/api/mcp.

Keys

A tf_platform_ key still signs the account routes above. It reaches no content route: the old ones are gone, and the Content API refuses it. Content work needs a tf_content_ key. Your agent account already has one. Register no longer issues tf_platform_ keys, but one an older account holds keeps working on the account routes.

Get a tf_content_ key

• From registration. POST /v1/platform/agent/register returns contentApiKey, a tf_content_ key. Its apiKey is null. Use contentApiKey for everything.
• From the dashboard. Sign in at tutorflow.io, open the Agent Platform dashboard, and create a key. The dashboard creates only tf_content_ keys. Choose Live or Test as the mode.

The raw key is shown once. Store it in your secrets manager.

Live and test keys

Read both classroom ids from GET /v1/platform/agent/account with a live key. With only a test key, GET /v1/content/classrooms lists the sandbox. See Test Mode.

Which key works where

A tf_platform_ key on the Content API gets this 401:

{
  "error": {
    "code": "content_platform_key_not_accepted",
    "message": "Agent Platform keys (tf_platform_) do not work on the Content API. Use a tf_content_ key: agent register returns one as contentApiKey, and the agent dashboard issues new ones.",
    "status": 401,
    "requestId": "..."
  }
}

A missing or unknown key on an account route gets 401 platform_invalid_api_key.

Rotate a key

Rotate or revoke keys in the Agent Platform dashboard. Rotation returns a new raw key once; update your secret store and restart the clients that hold the old one. Rotating a tf_platform_ key gives another tf_platform_ key, which still reaches only the account routes, so create a tf_content_ key instead and revoke the old one once nothing uses it.

The classroom in every URL

Every Content API route sits under a classroom: /v1/content/classrooms/{classroomId}/.... An agent account has one default classroom, created at registration. Read its id once and keep it:

curl https://api.tutorflow.io/v1/platform/agent/account \
  -H "Authorization: Bearer $TUTORFLOW_CONTENT_API_KEY"

{
  "defaultClassroomId": "00000000-0000-4000-8000-000000000010",
  "sandboxClassroomId": null,
  "contentApiBaseUrl": "https://api.tutorflow.io/v1/content",
  "contentApiUrls": {
    "listClassrooms": "GET /v1/content/classrooms",
    "generateCourse": "POST /v1/content/classrooms/00000000-0000-4000-8000-000000000010/courses/generate",
    "listCourses": "GET /v1/content/classrooms/00000000-0000-4000-8000-000000000010/courses",
    "generateSlides": "POST /v1/content/classrooms/00000000-0000-4000-8000-000000000010/slides/generate",
    "generateTest": "POST /v1/content/classrooms/00000000-0000-4000-8000-000000000010/tests/generate",
    "createVideo": "POST /v1/content/classrooms/00000000-0000-4000-8000-000000000010/videos"
  }
}

sandboxClassroomId stays null until the account has a test key.

What changes in the answers

Route map

{classroomId} is your defaultClassroomId. Paths on the right are under /v1/content/classrooms/{classroomId}. Every route in the left column was removed on 2026-10-16.

Courses: /v1/platform/courses

See Courses and Course chapters and lessons.

Modules: /v1/platform/modules

Tests: /v1/platform/tests

See Tests and Learners.

Slides: /v1/platform/slides

Videos: /v1/platform/videos

The Content API has no route that writes a whole narrated video from a prompt. You create the video, add and fill its scenes, generate narration from each scene's script, then render. See Videos and Video Rendering.

Games: /v1/platform/games

Evaluations: /v1/platform/evaluations

The request body is the same: evaluationType, questionText, learnerAnswer, referenceAnswer, rubric, maxScore, learnerExternalId or submitter, conceptTags, language, mode, clientMetadata, and the rest. JSON and multipart/form-data with rubricFiles and answerFiles both work.

Learners: /v1/platform/learners

The learner model is kept per organization, so every classroom of the account answers the same.

Webhook endpoints: /v1/platform/webhooks

See Webhooks for testing, rotation, delivery logs, and redelivery.

Webhooks

The /v1/platform/webhooks routes were removed on 2026-10-16. Your Platform webhook endpoints were copied to Content API endpoints for the same account, with the same URL and the same signing secret. Each copy starts active if the Platform endpoint was active. Events were mapped:

A Platform *.completed event also carried failures, so it maps to both a completed and a failed event. Note that video.render.completed means the mp4 is ready; the Platform's video.completed meant the scenes were written.

What your receiver has to change:

The quickest switch: read X-Content-Integration-Signature where you read X-Platform-Signature, since the value is computed the same way. Then branch on the new event names and payloads. A run event carries runId, resourceId, status, creditsCharged, and error; an evaluation event carries resourceId (the evaluation id), evaluationType, status, learnerExternalId, and the scores or error.

Old share links

Share links handed out before the removal keep working as links. A link of the form https://tutorflow.io/platform/{videos,slides,courses,tests,modules}/{shareToken} now redirects to the classroom public page of the copied content. When no classroom page matches, for example because the copy has no public page, the link shows a page that says the content has moved.

For new links, use the publicUrl the Content API returns on each resource.

Billing

There is one balance: the classroom credits of the organization behind your account. Content API calls and anything a person does in the TutorFlow editor both spend it.

• Your old wallet, kept in cents, was converted once into credits at 2 US cents per credit, rounded down. A wallet that still held only the untouched $1.00 trial grant, with no usage, was not converted. New accounts start with 50 trial credits.
• GET /v1/platform/agent/account answers credits and creditBalance. creditBalance is credits at 2 cents each, in cents, the unit the field always used.
• Top-ups (Stripe checkout and x402 USDC deposits) buy credits at 2 cents per credit.
• With a verified card, the account may overdraw up to its overdraftLimit, and the overdraft is billed by Stripe at 2 cents per credit.

See Pricing and Billing for the price of each call.

MCP

The MCP server at https://mcp.tutorflow.io/api/mcp runs its content tools on the Content API only. create_course, get_course_generation, list_courses, run_evaluation, and list_evaluations need a tf_content_ key and work in your default classroom (the sandbox for a test key). Called with a tf_platform_ key, they answer with an error that names tf_content_ keys and points to the Agent Platform dashboard; they no longer fall back to the removed routes. The account tools keep working with either key. To fix it, change the Authorization header in your MCP client configuration to Bearer tf_content_.... See MCP Integration.

Checklist

1. Get a tf_content_ key from registration or the dashboard, and store it.
2. Read defaultClassroomId from GET /v1/platform/agent/account.
3. Find the content you made before 2026-10-16 in that classroom with the Content API list routes.
4. Replace each removed route with its replacement above. Send topic instead of prompt.
5. Replace synchronous waits with run polling or *.generation.* webhooks.
6. Replace edit and share token handling with editorUrl and publicUrl.
7. Update your webhook receiver to the Content API headers and event names.
8. Switch the MCP client configuration to the tf_content_ key.