Obtain an Ethos API key scoped to your Colleague integration from the Ethos Integration Hub and authenticate by POSTing the key to the Ethos auth endpoint to receive a short-lived JWT
GET /api/sections with Accept: application/vnd.hedtech.integration.v{n}+json to retrieve the list of course sections; use limit and offset query parameters to page through results
For each section, record the id (GUID) and note the course, academicPeriod, and instructors embedded in the response
GET /api/section-registrations?section={sectionGuid}&limit=100 to retrieve all student registrations for a section; repeat with offset for large sections
Extract the registrant person GUIDs and GET /api/persons/{guid} to resolve student identity attributes such as credentials and names
Handle change-data events by polling the Ethos change-log endpoint for new section-registration events rather than re-fetching full payloads
Known gotchas
Ethos wraps Colleague data in HEDTECH Integration Framework (HIF) JSON schemas versioned per resource type — always specify the Accept header with the exact version you have mapped against, as version mismatches silently return a different schema
Colleague's Ethos layer does not support all fields that Banner's Ethos layer does; some person attributes (e.g., veteran status) are not returned — verify coverage against the Colleague-specific field support matrix
Ethos JWTs expire in 24 hours; long-running batch jobs must refresh the token before expiry or requests return 401 mid-run
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp