canonical: https://jentic.com/apis/corsizio.com/corsizio

# Corsizio API

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.

## For AI 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.

## Scope

Does not handle course content authoring, payment processing, or live-class video - use for reading Corsizio courses, events, registrations, and contacts only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Courses** — List courses and retrieve a single course by ID.
- **Events** — List events under a course and retrieve a single event by ID.
- **Registrations** — List registrations on an event and retrieve a single registration by ID.
- **Contacts** — List contacts and retrieve a single contact by ID.

## Why Jentic

- **Setup:** Wiring Corsizio by hand means learning its API key auth, pinning the v1 host, and writing your own paging code for courses, events, and registrations. Through Jentic you install once, import Corsizio from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Corsizio puts the course and event id in the URL path (/courses/{courseId}/events, /events/{eventId}/registrations), so a rule can pin your agent to one course or event: it can read that resource and nothing else. You choose the operations it may call, so it stays limited to the reads you allow.
- **Credential handling:** Your Corsizio API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list upcoming course events' or 'get registrations for an event', and Jentic returns the matching Corsizio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cvent API** — Enterprise event management platform with broader logistics and venue features than Corsizio.
- **Teachable API** — Online course platform focused on self-paced digital courses rather than scheduled events.
- **Meetup API** — Community event platform that can promote Corsizio events to a broader audience.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Corsizio API?

Yes. Because you run Jentic One yourself, your own rules decide which Corsizio operations the agent may call and which stored key it uses, so you can allow only the reads you want, such as GET /courses and GET /events/{eventId}/registrations. Since Corsizio carries the course and event id in the URL path, a rule can pin the agent to a single course or event, letting it read that resource and nothing else. The agent never gets write access, because all of these endpoints are read-only.