The common format for API requests is:
- https://yourdomain.campusconcourse.com/api?version=0&operation=your_operation&arg1=val1&...
Operations may have required and/or optional arguments. All data is returned
in the JSON format. See the documentation for each operation to understand its
functionality and arguments.
Go to Admin > System > API to view your base endpoint URL and key. You must be a system administrator to access this area and to make browser-based API requests.
Requests can also be made programmatically by supplying your API key in the X-AUTH-KEY request header. For example:
- curl -H "X-AUTH-KEY: your_api_key" "https://yourdomain.campusconcourse.com/api?version=0&operation=course_info&course_id=1"
The course_ids operation returns an array of pairs of internal course IDs and external IDs. Any parameter available in the Concourse search form may be used to filter the courses which are returned. For example:
- /api?version=0&operation=course_ids&year=2021&template=templates
Learn more about the course_ids operation with our API - Course Listing article.
The course_info operation returns a nested array of course and syllabus content. Either a course_id or external_id identifying a course is required. For example:
- /api?version=0&operation=course_info&external_id=ACCT_101_SPR_2025
Learn more about the course_info operation with our API - Syllabus Content article.
The syllabus_access operation returns a nested array of users who have accessed a syllabus. Either a course_id or external_id identifying a course is required. For example:
- /api?version=0&operation=syllabus_access&external_id=ACCT_101_SPR_2025
Learn more about the syllabus_access operation with our API - Syllabus Access article.
The change_log operation returns a nested array of users and systems that have changed a syllabus. Either a course_id or external_id identifying a course is required. For example:
- /api?version=0&operation=change_log&external_id=ACCT_101_SPR_2025
Learn more about the change_log operation with our API - Syllabus Changes article.
HTTP response codes are used for the following general errors:
Code | Error | Resolution |
400 | Request malformed | Check URL parameters |
403 | Incorrect API key | Check the provided API key |
404 | Specified resource not found | Check for matching resource |
500 | API key is not configured | Submit a ticket |