CE-Go API
★ Only Publicly Available OpenAPI DocumentEducationLmsapiKey9 EndpointsREST
For Agents
List CE-Go continuing education events, courses, and registered users, and subscribe to event-ended webhooks. Pull CE/CEU attendance data into reporting or certification flows.
Use for: I need to list every continuing education event in CE-Go, Get all users registered for a specific CE-Go conference, List the courses available on the CE-Go account, Subscribe to a webhook that fires when an event ends
Not supported: Does not handle payment processing, certificate generation, or course content authoring — use for retrieving CE event, course, and registration data and managing webhook subscriptions only.
Jentic publishes the only available OpenAPI specification for the CE-Go API, keeping it validated and agent-ready. CE-Go is an event management platform for Continuing Education and CEU events used by associations, training providers, and certifying bodies. The API exposes endpoints for listing conferences (events) and courses, retrieving the users registered against each event or course, and subscribing to webhooks that fire when events end. The base URL sits on the Zapier-flavoured V3 route, which is the integration surface CE-Go exposes to third parties.
Install Jentic One Beta
Connect the CE-Go API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CE-Go 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 CE-Go API.
List continuing education events (conferences) on the CE-Go account
List courses configured for the account with their metadata
Retrieve the users registered against a specific event or course
Pull users across all events or all courses in one call
Subscribe to event-ended webhooks for downstream certification or reporting workflows
Unsubscribe from existing webhook subscriptions to clean up integrations
Use Cases
Patterns agents use CE-Go API for, with concrete tasks.
★ Continuing Education Attendance Sync
Associations push CE-Go attendance data into their member systems so members get credit for attending events. An agent calls the conferences and conferences/{eventId}/users endpoints, joins the records to internal member ids, and writes credit awards back to the association management system. This automates a step that is otherwise a manual roster export.
GET /conferences, then for each event id GET /conferences/{eventId}/users and post the matched members to the association system
Event-Ended Certificate Issuance
When a CE event ends, certificates need to go out to attendees. An agent subscribes to the event-ended webhook via /webhooks/subscribe, then on each delivered event fetches the user list and triggers certificate generation. The /webhooks/samples/event-ended endpoint is used during build to validate the agent's parser before going live.
POST a subscription to /webhooks/subscribe for the event-ended topic, then on each event call GET /conferences/{eventId}/users and issue certificates
Cross-Course Learner Reporting
Training operations teams need a consolidated view of which learners completed which courses across the account. The /courses/users endpoint returns users across every course, suitable for piping into a BI tool or weekly summary email. An agent can run this on a schedule and surface deltas since the last run.
GET /courses/users and produce a weekly summary of learners grouped by course
AI Agent Integration via Jentic
An education operations agent uses Jentic to discover CE-Go endpoints and execute calls without holding the CE-Go API key directly. The same agent can chain CE-Go data with email or association management APIs while credentials stay in the Jentic vault.
Use Jentic to search 'list users for a CE-Go event', load the schema for /conferences/{eventId}/users, and execute for the most recent event
Key Endpoints
9 endpoints — jentic publishes the only available openapi specification for the ce-go api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/conferences
List events
GET
/conferences/{eventId}/users
List users for an event
GET
/courses
List courses
GET
/courses/{courseId}/users
List users for a course
POST
/webhooks/subscribe
Subscribe to a webhook
DELETE
/webhooks/unsubscribe/{subscriptionId}
Unsubscribe from a webhook
GET
/conferences
List events
GET
/conferences/{eventId}/users
List users for an event
GET
/courses
List courses
GET
/courses/{courseId}/users
List users for a course
POST
/webhooks/subscribe
Subscribe to a webhook
DELETE
/webhooks/unsubscribe/{subscriptionId}
Unsubscribe from a webhook
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
CE-Go API keys are stored encrypted in the Jentic vault. Agents call /conferences and /webhooks endpoints through scoped execution requests; the raw Authorization header value never enters agent context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'list users for a CE event') and Jentic returns the matching CE-Go operation with its input schema, so the agent picks the right endpoint without browsing the integration docs.
Time to first call
Direct CE-Go integration: half a day to a day for auth, paginated pulls, and webhook subscription handling. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CE-Go API through Jentic.
Why is there no official OpenAPI spec for the CE-Go API?
CE-Go publishes its API through a Zapier-flavoured integration surface and supporting docs rather than a public OpenAPI artifact. Jentic generates and maintains this spec so that AI agents and developers can call CE-Go 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 CE-Go API use?
The CE-Go API uses an API key passed in the Authorization header. Through Jentic the key sits in the encrypted vault and is injected at execution time so the agent never holds it directly.
Can I get the list of users registered for a CE-Go event?
Yes. GET /conferences/{eventId}/users returns the users registered for the given event id. There is also /conferences/users for users across all events and an equivalent pair under /courses for course registrations.
What are the rate limits for the CE-Go API?
The OpenAPI spec does not declare specific rate limits. CE-Go applies fair-use throttling at the API key level — design integrations to back off on 429 responses and avoid pulling the full /courses/users list more than necessary.
How do I subscribe to event-ended webhooks through Jentic?
Search Jentic for 'subscribe to a CE-Go event-ended webhook', load the schema for POST /webhooks/subscribe, and execute with the target URL. The /webhooks/samples/event-ended endpoint provides a fixture for testing the parser before going live.
Is the CE-Go API free?
API access is included with paid CE-Go plans rather than sold separately. Pricing details are on ce-go.com — there is no public free tier for the API itself.
GET STARTED