Miho API

Name: Miho API API
Brand: Miho API
Availability: InStock

✓ Official Vendor SpecEducationLmsapiKey3 EndpointsREST

For Agents

List available courses on Miho and manage student enrollments through 3 operations on a v2 LMS API.

Quickstart

Get started with Miho API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list miho courses"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Miho API API.

List courses available in the Miho catalogue with /courses

Read enrollment records for a learner or course with /enrollments

Enrol a learner in a chosen course by creating an enrollment record

Authenticate every request with an API key passed in the Authorization header

Build a thin course-catalogue widget on top of an external site without proxying the Miho web UI

GET STARTED

Start building with Miho API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Miho API API for, with concrete tasks.

★ Course Catalogue Widget

Build a course catalogue widget on a marketing site by calling /courses to list the active offerings on Miho. The response feeds a card grid that links each course to its detail page, and can be cached to keep traffic off the LMS for browse-only sessions. This avoids embedding the full Miho web UI when a thin marketing experience is enough.

Call GET /courses, render each course as a card with title and description, and link the card to the Miho course detail page

Automatic Enrollment on Purchase

Connect a checkout flow to Miho by creating an enrollment record on /enrollments after a successful payment. The integration receives the learner id and chosen course id from the upstream order system and posts them to /enrollments to grant access. This automates the gap between commerce and learning delivery.

On successful payment, POST to /enrollments with the learner id and course id, then read the response back to confirm the enrollment record was created

Learner Enrollment Lookup

Surface a learner's current enrollments on a customer-success dashboard or in a support agent's view by calling /enrollments filtered to a specific learner. The result lets the operator answer questions about course progress and access without logging into the Miho UI per ticket.

Call GET /enrollments filtered by the learner id and return the active course ids in a single response

Agent Integration via Jentic

An AI agent built on Jentic can search for the Miho course and enrollment operations by intent and execute them without holding the API key in agent context. Jentic's MAXsystem holds the credential and returns scoped access at call time, which is helpful when the same agent automates onboarding across multiple education tools.

Use Jentic search for 'list miho courses', load the GET /courses operation, execute it, and feed the returned course ids into a follow-up enrollment call

Key Endpoints

3 endpoints — miho is a learning management platform exposing a small v2 rest api focused on courses and enrollments.

METHOD

PATH

DESCRIPTION

GET

/courses

List the available course catalogue

GET

/enrollments

List enrollment records, filterable by learner or course

POST

/enrollments

Create an enrollment record for a learner in a course

GET

/courses

List the available course catalogue

GET

/enrollments

List enrollment records, filterable by learner or course

POST

/enrollments

Create an enrollment record for a learner in a course

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Miho API key is stored encrypted in the Jentic vault. Agents receive scoped execution tokens at call time and never hold the raw key, which matters for support and onboarding agents that span multiple education tools.

Intent-based discovery

Agents search by intent such as 'list miho courses' or 'enrol a learner in a miho course' and Jentic returns the matching operation with its full input schema, so the agent can call the right endpoint without reading the docs.

Time to first call

Direct integration: a few hours for a 3-endpoint surface with simple key auth. Through Jentic: under 30 minutes from search to first executed call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Schoology

K-12 LMS API covering courses, sections, and enrollments

Choose Schoology when the deployment is a K-12 school district; choose Miho when Miho is the existing platform

Alternative

Moodle

Open-source LMS API covering courses, users, and enrollments

Choose Moodle when you self-host the LMS; choose Miho for its hosted v2 surface

Alternative

Teachable

Hosted course platform with checkout and enrollment APIs

Choose Teachable when you also need built-in commerce; choose Miho when you have a separate checkout that posts enrollments

FAQs

Specific to using Miho API API through Jentic.

What authentication does the Miho API use?

The Miho API expects an API key passed as the Authorization header. Through Jentic the key is held in the Jentic vault and a scoped execution token is granted at call time, so the agent never holds the raw key.

Can I create an enrollment programmatically?

Yes. POST /enrollments with the learner id and course id to grant the learner access to the course. Read the response to confirm the enrollment record was created. This is the integration point for automating fulfilment after a course purchase.

What are the rate limits for the Miho API?

The OpenAPI spec does not declare explicit rate limits. Treat the API as standard HTTPS, respect any 429 responses with exponential backoff, and check Miho's account dashboard or your contract for the contractual ceiling.

How do I list Miho courses through Jentic?

Install the Jentic SDK with pip install jentic, search for 'list miho courses', load the GET /courses operation, and execute it. Sign up at https://app.jentic.com/sign-up to get a Jentic agent key.

Why is the spec only 3 endpoints?

This OpenAPI spec covers the courses and enrollments slice of Miho's wider platform. It is the minimum surface needed for catalogue display and enrollment automation. Additional Miho features such as content delivery or progress tracking are not exposed in this version of the spec.