canonical: https://jentic.com/apis/udemy.com/udemy

# Udemy Instructor API

The Udemy Instructor API allows instructors to programmatically access and manage their courses, reviews, and performance data on the Udemy platform. Instructors can retrieve course listings, student reviews, Q&A threads, course performance metrics, and revenue reports. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically list instructor courses, get course details. Covers 6 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for education only.

## Capabilities

- List instructor courses
- Get course details
- Integrate Udemy Instructor API into automated workflows
- Query and filter Udemy Instructor API records by parameters
- Monitor Udemy Instructor API operational status and events

## Use cases

### Education Operations

Use the Udemy Instructor API to perform education operations programmatically. The API provides 6 endpoints covering core functionality including list instructor courses, get course details, list course reviews.

Example prompt: Call GET `/taught-courses/courses` to list instructor courses

### Automated Courses Management

Automate courses operations by combining multiple Udemy Instructor API endpoints. Agents can get course details and then list course reviews in a single workflow.

Example prompt: Call GET `/taught-courses/courses/{course_id}` to get course details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Udemy Instructor API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'list instructor courses', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/taught-courses/courses` | List instructor courses |
| GET | `/taught-courses/courses/{course_id}` | Get course details |
| GET | `/taught-courses/courses/{course_id}/reviews` | List course reviews |
| GET | `/taught-courses/courses/{course_id}/questions` | List course Q&A threads |
| GET | `/taught-courses/courses/{course_id}/performance` | Get course performance metrics |
| GET | `/revenue-report` | Get revenue report |

## Key resources

- **Courses** — Manage and retrieve instructor courses
- **Reviews** — Access course reviews
- **QA** — Access course Q&A threads
- **Performance** — Course performance and revenue analytics

## Why Jentic

- **Setup:** Wiring the Udemy Instructor API by hand means attaching a bearer token on every call, pointing at the instructor-api host, and matching each course, review, and revenue operation to its request shape yourself. Through Jentic you install once, import the Udemy Instructor API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Udemy puts the course id in the URL path (`/taught-courses/courses/{course_id}`), so a rule can pin your agent to one course: it can read that course, its reviews, questions, and performance and nothing else. You choose the operations it may call, so the revenue report is not included unless you add it.
- **Credential handling:** Your Udemy token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list my taught courses' or 'read a course's reviews', and Jentic returns the matching Udemy Instructor API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Schoology** — Alternative education API
- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows

## FAQ

### What authentication does the Udemy Instructor API use?

The Udemy Instructor API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list instructor courses with the Udemy Instructor API?

Yes. Use the GET `/taught-courses/courses` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Udemy Instructor API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list instructor courses through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list instructor courses'. Jentic returns the matching Udemy Instructor API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Udemy Instructor API have?

The Udemy Instructor API exposes 6 endpoints covering courses, reviews, qa operations.

### Can I limit what my agent is allowed to do with the Udemy Instructor API?

Yes. Because you run Jentic One yourself, your own rules decide which Udemy operations and which credentials the agent may use. Udemy puts the course id in the URL path (`/taught-courses/courses/{course_id}`), so a rule can pin the agent to a single course and let it read only that course, its reviews, its questions, and its performance metrics. You also choose which operations are exposed, so the revenue report (GET /revenue-report) stays out of reach unless you add it.