/udemy/courses

POST /api/udemy/courses

Price: 1 credit

Get Udemy (udemy.com) course details by course slug, numeric id, or course URL

How to use it

Get full details of a Udemy (udemy.com) course by slug ('100-days-of-code'), numeric course id, or course URL. Returns id, alias, course_title, headline, description, image, web_url, is_paid, price, price_currency, rating, review_count, student_count, lecture_count, level, content_info, duration_seconds, estimated_content_length, has_certificate, coding_exercise_count, assignment_count, quiz_count, published_quiz_count, practice_test_count, article_count, additional_asset_count, language, category, subcategory, objectives_summary, what_you_will_learn, requirements, target_audiences, caption_languages, instructors (id/name/job_title/image), created_at, published_at, and updated_date. Use an instructor id with the instructors endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• course string required — Udemy course slug ('100-days-of-code'), numeric course id, or course URL. (examples: "100-days-of-code", "2776760", "https://www.udemy.com/course/100-days-of-code/"; minLength: 1)

Response

• @type string (default: "UdemyCourse")
• id string required
• alias string nullable
• course_title string required
• headline string nullable
• description string nullable
• image string nullable
• web_url string required
• is_paid boolean nullable
• price number nullable
• price_currency string nullable
• rating number nullable
• review_count integer nullable
• student_count integer nullable
• lecture_count integer nullable
• level string nullable
• content_info string nullable
• duration_seconds integer nullable
• estimated_content_length integer nullable
• has_certificate boolean nullable
• coding_exercise_count integer nullable
• assignment_count integer nullable
• quiz_count integer nullable
• published_quiz_count integer nullable
• practice_test_count integer nullable
• article_count integer nullable
• additional_asset_count integer nullable
• language string nullable
• category string nullable
• subcategory string nullable
• objectives_summary array (default: [])
• what_you_will_learn array (default: [])
• requirements array (default: [])
• target_audiences array (default: [])
• caption_languages array (default: [])
• instructors array (default: [])
  • @type string (default: "UdemyCourseInstructor")
  • id string required
  • name string required
  • job_title string nullable
  • image string nullable
  • alias string nullable
  • web_url string nullable
• created_at integer nullable
• published_at integer nullable
• updated_date string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Course not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.