Corsizio API
★ Only Publicly Available OpenAPI DocumentEducationStudent ManagementapiKey8 EndpointsREST
For Agents
Read course catalogues, list scheduled events and their registrations, and look up contacts for the Corsizio course-registration platform. API-key authentication via the Authorization header.
Use for: List all the courses we currently offer on Corsizio, Get the details of a specific course by its ID, List the upcoming events for a course, Retrieve the registration list for an event
Not supported: Does not handle course content authoring, payment processing, or live-class video — use for reading Corsizio courses, events, registrations, and contacts only.
Jentic publishes the only available OpenAPI specification for Corsizio API, keeping it validated and agent-ready. The Corsizio API gives course providers programmatic read access to their course catalogue, scheduled events, registrations, and contact records. Authentication is via an API key in the Authorization header, and the eight endpoints cover listing and reading courses, listing the events under a course, listing registrations on an event, and looking up individual registrations or contacts.
Install Jentic One Beta
Connect the Corsizio API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Corsizio API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Corsizio API.
List every course offered by a Corsizio account so a website or chatbot can render an up-to-date catalogue
Retrieve an individual course by ID to display its full description, duration, and pricing
List all scheduled events under a course to surface upcoming session dates and seat availability
Get a single event by ID for confirmation pages and calendar invites
List registrations on an event to drive attendance reports and follow-up email sequences
Retrieve an individual registration by ID to look up payment status and attendee details
List and look up contact records to power CRM sync and audience segmentation
Use Cases
Patterns agents use Corsizio API for, with concrete tasks.
★ Public Course Catalogue Page
Render an always-fresh course catalogue on the provider's website by pulling the full course list and the events under each course on a schedule. Visitors see live seat counts, dates, and prices without an editor having to update a CMS.
Call GET /courses to list all courses, then for each course call GET /courses/{courseId}/events to fetch upcoming sessions, and render a static catalogue page from the merged result.
Attendance and Follow-Up Reporting
After an event runs, pull the registration list to feed an attendance report and trigger follow-up emails — feedback surveys to attendees, a re-engagement note to no-shows. Each registration links back to a contact record for richer email personalisation.
Call GET /events/{eventId}/registrations, then for each registration call GET /contacts/{contactId} to pull the contact's email, and queue follow-up messages via your email tool.
CRM Contact Sync
Sync Corsizio contacts into the company's CRM so that course buyers appear alongside other customer records and can be enrolled in nurture sequences. The contacts endpoints support both bulk pulls and per-record refresh based on changed registrations.
Call GET /contacts on a daily schedule and upsert each record into the CRM, using GET /contacts/{contactId} for targeted refreshes when a new registration is observed.
AI Agent Course Assistant via Jentic
An AI assistant on the course provider's site answers questions like 'when is the next ICF coaching workshop?' or 'how many seats are left on the May intake?' by searching Jentic for the right Corsizio operation and returning the answer in plain language. The agent handles only intents, not endpoint paths.
Search Jentic for 'list course events' or 'list registrations', load GET /courses/{courseId}/events or GET /events/{eventId}/registrations, and execute with the user's chosen course or event ID to compose the answer.
Key Endpoints
8 endpoints — jentic publishes the only available openapi specification for corsizio api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/courses
List courses
GET
/courses/{courseId}
Get a course by ID
GET
/courses/{courseId}/events
List events under a course
GET
/events/{eventId}
Get an event by ID
GET
/events/{eventId}/registrations
List registrations on an event
GET
/contacts
List contacts
GET
/courses
List courses
GET
/courses/{courseId}
Get a course by ID
GET
/courses/{courseId}/events
List events under a course
GET
/events/{eventId}
Get an event by ID
GET
/events/{eventId}/registrations
List registrations on an event
GET
/contacts
List contacts
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Corsizio API key is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution handle — the key is injected into the Authorization header at call time and never enters the agent's prompt or logs.
Intent-based discovery
Agents search by intent (e.g., 'list Corsizio course events' or 'get registration details') and Jentic returns the matching operation with its input and response schemas, so the agent picks the right endpoint without browsing Corsizio documentation.
Time to first call
Direct Corsizio integration: half a day for auth and pagination handling. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Corsizio API through Jentic.
Why is there no official OpenAPI spec for Corsizio API?
Corsizio publishes API documentation on its website but not a single OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Corsizio API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Corsizio API use?
The API uses an API-key scheme: every request must include an Authorization header containing the key issued from the Corsizio dashboard. Through Jentic, the key is held in the encrypted vault and added to the header at execution time so it never enters the agent's prompt context.
Can I list registrations for a Corsizio event?
Yes. GET /events/{eventId}/registrations returns the registrations attached to an event, which is the canonical primitive for attendance reports and post-event automation.
Can I create or modify courses with this API?
No. The current spec exposes read-only endpoints — courses, events, registrations, and contacts can be listed and fetched by ID, but creation and updates are not part of this surface. Use the Corsizio dashboard for content editing.
What are the rate limits for the Corsizio API?
The OpenAPI spec does not declare numeric rate limits. Treat HTTP 429 responses as authoritative, back off using the Retry-After header where present, and consult the Corsizio support team for plan-specific limits before high-volume polling.
How do I list events for a course through Jentic?
Search Jentic for 'list Corsizio course events', load GET /courses/{courseId}/events, and execute it with the course ID. Jentic returns the operation schema so the agent does not need to parse Corsizio docs to know which fields come back.
GET STARTED