/coursera/courses/search

POST /api/coursera/courses/search

Price: 5 credits

Search the Coursera (coursera.org) catalog (courses, specializations, certificates, degrees)

How to use it

Search the Coursera (coursera.org) learning catalog by keyword across courses, specializations, professional certificates and degrees. Filter by topic, level, duration, product_type, language, subtitle_language, skill and partner; order by relevance or newest. Returns id, name, tagline, product_type, canonical_type, marketing_type, rating, rating_count, difficulty_level, duration, is_free, is_credit_eligible, is_part_of_coursera_plus, image, partners, partner_logos, skills, fully_translated_languages, subtitle_languages, web_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "python", "machine learning", "excel"; minLength: 1)
• count integer required — Max number of results to return (min: 1)
• topic string nullable — Filter by subject / category (one of: "Business", "Artificial Intelligence", "Data Science", "Computer Science", "Information Technology", "Personal Development", "Healthcare", "Language Learning", "Social Sciences", "Arts and Humanities", "Physical Science and Engineering", "Math and Logic")
• level string nullable — Filter by difficulty level (one of: "Beginner", "Intermediate", "Advanced", "Mixed")
• duration string nullable — Filter by learning duration bucket (one of: "Less Than 2 Hours", "1-4 Weeks", "1-3 Months", "3-6 Months", "6-12 Months", "1-4 Years")
• product_type string nullable — Filter by learning-product type (one of: "Courses", "Guided Projects", "Projects", "Specializations", "Professional Certificates", "MasterTrack Certificates", "Degrees")
• language string nullable — Filter by fully-translated language name (e.g. 'English', 'Spanish')
• subtitle_language string nullable — Filter by available subtitle language name
• skill string nullable — Filter by skill name (e.g. 'Python', 'Data Analysis')
• partner string nullable — Filter by educator / partner name (e.g. 'Google', 'IBM')
• sort string — Result ordering (default: "BEST_MATCH"; one of: "BEST_MATCH", "NEW")

Response

• @type string (default: "CourseraSearchProduct")
• id string required
• name string required
• tagline string nullable
• product_type string nullable
• canonical_type string nullable
• marketing_type string nullable
• rating number nullable
• rating_count integer nullable
• difficulty_level string nullable
• duration string nullable
• is_free boolean nullable
• is_credit_eligible boolean nullable
• is_part_of_coursera_plus boolean nullable
• image string nullable
• partners array (default: [])
• partner_logos array (default: [])
• skills array (default: [])
• fully_translated_languages array (default: [])
• subtitle_languages array (default: [])
• web_url string required

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 — The entity was not found, or a precondition failed 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.