assist.org APIwww.assist.org ↗
Retrieve California Community College course articulation agreements to UC/CSU institutions via 3 endpoints. Look up which CCC courses satisfy CS transfer requirements at UC Davis.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/57311141-c86d-4049-94c2-b968e560c2fb/list_cccs' \ -H 'X-API-Key: $PARSE_API_KEY'
List all California Community Colleges with their IDs and names. Returns the full set of 116 CCCs available on ASSIST.org.
No input parameters required.
{
"type": "object",
"fields": {
"cccs": "array of objects with id (integer) and name (string)",
"total": "integer - total number of CCCs"
},
"sample": {
"data": {
"cccs": [
{
"id": 110,
"name": "Allan Hancock College"
},
{
"id": 27,
"name": "American River College"
},
{
"id": 121,
"name": "Antelope Valley College"
}
],
"total": 116
},
"status": "success"
}
}About the assist.org API
The ASSIST.org API exposes 3 endpoints for querying California Community College course articulation agreements with UC/CSU receiving institutions. The list_cccs endpoint returns all 116 participating CCCs with their IDs and names. The get_single_articulation and get_all_articulations endpoints return course mapping objects that show exactly which CCC courses satisfy UC Davis Computer Science B.S. requirements, section by section.
What the API Returns
The list_cccs endpoint returns a flat array of all 116 California Community Colleges indexed on ASSIST.org, each with an integer id and a name string. These IDs are the lookup keys for the articulation endpoints. The total field confirms the full count in the response.
Articulation Data Structure
get_single_articulation accepts either a ccc_id integer or a case-insensitive ccc_name substring, plus an optional academic_year_id (e.g. 76 for 2025–2026, 75 for 2024–2025). The response includes a status field — success, no_agreement, or error — along with course_mappings, an array of objects each containing a section label, a uc_davis_course requirement, and the ccc_equivalent course or courses that satisfy it. The receiving_institution is always University of California, Davis and the major is always Computer Science B.S.
Bulk Retrieval and Pagination
get_all_articulations runs the same articulation lookup across multiple CCCs using offset and limit parameters against the alphabetically sorted CCC list. The response breaks down results into success_count, no_agreement_count, and error_count so you can audit coverage gaps at a glance. Because each CCC takes several seconds to process, the recommended limit per call is 1–2 to stay within timeout thresholds. total_cccs_available tells you how many CCCs remain beyond your current page.
Coverage and Academic Years
All articulation data reflects Computer Science B.S. requirements at UC Davis. Academic year coverage is controlled by the academic_year_id parameter; omitting it defaults to a current year. Not all CCCs have an active articulation agreement for this major — the no_agreement status indicates those cases explicitly.
- Build a transfer planning tool that shows prospective CS students which courses at their local CCC satisfy UC Davis requirements
- Audit all 116 CCCs for CS articulation coverage by iterating
get_all_articulationswith pagination offsets - Compare articulation agreements across academic years using the
academic_year_idparameter to detect changes in accepted equivalent courses - Identify CCCs with no CS articulation agreement using the
no_agreementstatus field in bulk results - Populate a course equivalency database keyed by
ccc_idfor integration with a student advising platform - Track year-over-year changes in
course_mappingsto alert students when previously accepted equivalencies are dropped
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does ASSIST.org have an official developer API?+
What does the `course_mappings` field contain, and how is it structured?+
course_mappings has three fields: section (a label grouping related requirements), uc_davis_course (the specific UC Davis CS course the requirement belongs to), and ccc_equivalent (the course or courses at the community college that satisfy it). For CCCs with status: no_agreement, the course_mappings array will be empty.Why is the recommended `limit` only 1–2 per call to `get_all_articulations`?+
get_all_articulations involves multiple upstream lookups that take roughly 6 seconds each. Using a small limit and incrementing offset across sequential calls avoids HTTP timeout failures. The cccs_processed, offset, and total_cccs_available fields in the response let you track pagination state.Does the API cover articulation agreements for majors other than Computer Science, or for institutions other than UC Davis?+
major and receiving_institution fields in every response reflect this fixed scope. You can fork this API on Parse and revise it to target a different major or receiving institution endpoint.Does the API return historical articulation data for years before 2024–2025?+
academic_year_id parameter supports values like 75 (2024–2025) and 76 (2025–2026), but coverage for earlier years depends on what ASSIST.org retains. If you need data for a specific prior year not reflected in the current responses, you can fork this API on Parse and revise the academic year mapping to test additional year IDs.