GO1 APIs for AI Agents
EducationLmsJentic-Generated DocumentsBearer tokenOAuth 2.0Agent Ready
For Agents
APIs2 in catalogue
Endpoints37 indexed
AuthBearer token / OAuth 2.0
ProvenanceJentic-generated documents
An agent can sign in to a GO1 organisation over OAuth 2.0, read the connected account, enrol learners in specific learning objects, track completion, and add or remove courses from curated collections. It can also fetch SCORM package URLs and configure SAML attribute mappings for SSO-driven learner provisioning.
GO1 aggregates courses from many training providers behind one platform, so an agent works against a single multi-vendor learning surface rather than one publisher's library. The APIs split cleanly into a lightweight OAuth sign-in step and a wider v2 platform for enrolments, collections, and content.
Use for: Signing in to a GO1 organisation, enrolling learners in learning objects, curating collections, and pulling SCORM packages for LMS embedding
Not supported: course authoring, video hosting, instructor-led training, declared rate limits, content payment processing
Credentials: Both APIs use OAuth 2.0, and the same GO1 OAuth client credentials cover sign-in on the Learning Platform API and the bearer-token calls on the wider GO1 API.
All 2 GO1 OpenAPI documents are Jentic-generated and indexed by Jentic, kept validated and agent-ready.
GO1 is an online learning platform whose APIs let you authenticate against a GO1 organisation, enrol learners in courses, curate collections of learning objects, and pull SCORM packages for embedding in an LMS. The Jentic-published specs cover the OAuth 2.0 sign-in surface and the wider v2 platform that manages enrolments, learning content, and SSO attribute mappings.
GO1 API Catalog
2 APIs across 1 product group.
Which GO1 API should I use?
| I want to... | Use |
|---|---|
| Sign in and confirm which GO1 organisation a token belongs to | GO1 Learning Platform API |
| Enrol learners, manage collections, or fetch SCORM packages | GO1 API |
| Read the authenticated account profile | GO1 Learning Platform API |
Install Jentic One Beta
Connect the GO1 APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GO1 APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgo1.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgo1.com" | 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.
Once connected, ask your agent something like: “sign in to go1 and enrol a learner in a course”.
What AI Agents Can Do with GO1
Each workflow spans multiple GO1 APIs. Jentic routes each operation to the right API automatically.
Authenticated compliance enrolment
An agent runs the OAuth authorisation code flow on the Learning Platform API to obtain a bearer token, confirms the organisation with the account endpoint, then uses the GO1 API to enrol every employee in a mandatory learning object and read completion status.
Example prompt:
Exchange the OAuth code for a token, verify the organisation account, then enrol every user in department Engineering into the data-protection learning object.
APIs used
GO1 Learning Platform API + GO1 API
Tenant-safe curated learning paths
Before assembling a role-specific learning path, the agent verifies the connected tenant with the Learning Platform API account endpoint, then adds and removes courses on a specific GO1 API collection so updates never land in the wrong customer's workspace.
Example prompt:
Confirm the account tenant, then add the three newest leadership courses to the Manager Onboarding collection and remove any deprecated items.
APIs used
GO1 Learning Platform API + GO1 API
SSO-driven learner provisioning
For partners provisioning learners over SAML, the agent signs in through the Learning Platform API, then configures SAML custom attribute mappings and manages OAuth client credentials on the GO1 API so identity attributes flow from the partner IdP into GO1 records.
Example prompt:
Sign in, then create a SAML custom attribute mapping for employee_id on the partner staff client.
APIs used
GO1 Learning Platform API + GO1 API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring GO1 by hand means running the OAuth 2.0 authorisation code flow against the auth host, then coordinating bearer calls against the separate v2 platform host for enrolments and collections. Through Jentic you install once, add the GO1 APIs from the Jentic directory, store the credential once, and your agent calls both surfaces.
Permission scoping
GO1 puts identifiers such as the collection id in the URL path, so your own rules can pin an agent to one collection and to a chosen set of operations. It can sign in, verify the account, and enrol users only when you include those operations, and nothing else.
Credential isolation
Your GO1 OAuth client id, secret, and refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as enrol a GO1 user or exchange a GO1 OAuth code, and Jentic returns the matching operation with its input schema, so the agent picks the right API without reading the developer docs.
FAQs
Specific to using GO1 APIs through Jentic.
How do the two GO1 APIs fit together?
The Learning Platform API is the lightweight sign-in surface: it runs the OAuth 2.0 authorisation code flow and reads the connected account. Once you hold a valid bearer token, the wider GO1 API handles enrolments, learning objects, collections, and SAML configuration. Most workflows start on the Learning Platform API and then move to the GO1 API.
Does one credential work across both GO1 APIs?
Yes. Both APIs use OAuth 2.0, and the same GO1 OAuth client credentials that sign you in on the Learning Platform API produce the bearer token you use for calls to the GO1 API. You register one client and reuse it across the portfolio.
Can an agent run a full training rollout across these APIs?
Yes. An agent authenticates through the Learning Platform API, confirms the organisation, then uses the GO1 API to enrol users in a learning object, add courses to a collection, and read completion. The two surfaces chain into a single automated flow.
Why does Jentic publish these specs?
GO1 ships developer reference documentation but does not publish OpenAPI specifications. Jentic generates and maintains both specs, validates them against the live APIs, and keeps them agent-ready so tools can call GO1 through structured schemas.
Can these APIs embed courses in another LMS?
Yes. The GO1 API returns SCORM package URLs for learning objects, which an external LMS can launch. The Learning Platform API handles the sign-in and account verification that precede fetching that content.
How does an agent avoid cross-tenant mistakes when one integration serves many GO1 customers?
The Learning Platform API account endpoint returns the organisation a token belongs to. An agent reads it to assert the tenant matches the expected customer before issuing any enrolment or collection change on the GO1 API.
If you need a different Education vendor
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.