Yoshuko documentation

Everything you can do in Yoshuko — building courses, selling them from your own storefront, teaching and marking learners — explained step by step, with a screenshot of every screen. The parts that can be automated are documented as an API that an AI agent or a script can call with a key.

Get started For AI Agents

Find your way in

• I create and sell courses

  ---

  Build a curriculum of units, lessons, quizzes and assignments, publish it, sell it from your storefront and follow every learner's progress.

  Creator guides

• I'm learning on Yoshuko

  ---

  Find and join a course, work through lessons, take quizzes and download your certificate.

  Learner guides

• I'm an AI agent, or I'm building one

  ---

  How to authenticate, what a key can do, and copy-paste calls in curl, Python and JavaScript. Machine-readable: llms.txt · openapi.json · capabilities.json

  Start here

• My account and privacy

  ---

  Signing in, two-factor authentication, passwords, your data, cookies, and reporting a problem.

  Account & privacy

Popular tasks

Getting going

• Create your account
• Set up your organisation
• Publish your first course
• Is Yoshuko right for me?

Building and teaching

• Organise units and lessons
• Add quizzes and assignments
• Enrol a whole class at once
• Mark work in the gradebook

Selling

• Write a listing that sells
• Use your own domain
• Get paid with Stripe
• Recruit affiliates

Automate Yoshuko in three steps

1. Subscribe to any paid plan. API access is included on every plan — see pricing.
2. Create a key in Organization → API Keys and choose what it may do. About three minutes — follow the guide.
3. Make your first call. One curl confirms the key works and shows exactly what it may do — try it.

An API key can create, read, update and delete courses, units and lessons (including quizzes and assignments) and read or update organisation settings. The capability list shows everything else Yoshuko does and marks honestly which parts are still web-app only.

How these docs stay accurate

The screenshots are captured by Yoshuko's automated browser tests, the API reference is generated from the live API schema, and the capability list comes from the same task model the test suite drives. When the product changes, the docs are rebuilt from those sources and checked before they are published.