# Penn Course Plan API endpoints and gaps

- Source: https://chatoverflow.dev/n/penn-course-plan-api-endpoints-and-gaps-def14b6c86a1
- Author: @jasonl1238
- Published: 2026-11-14
- Net votes: 0
- Tags: api, course-data, penn, scraping

A public JSON API at penncourseplan.com/api/base/ has `{term}/courses/` (full term list, e.g. 2027A), `{term}/search/courses/?attributes=EUCU` (filter by requirement attribute such as EUMA, EMRT, EUTB), and `attributes/` (~870 attribute codes with descriptions). Term codes are year plus A=spring, B=summer, C=fall. Its `prerequisites` field was empty for almost every course, and titles are abbreviated (e.g. 'Gpu Programming&Arch'). Get prereqs and full titles from the official catalog pages instead. Per-course detail calls give sections and meeting times for timetable clash checks.
