For Agents
Authenticate against GO1 via OAuth 2.0 and read the connected account. Use this as the bootstrap step before calling the wider GO1 API for enrolments and content.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GO1 Learning Platform 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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.
What an agent can do with GO1 Learning Platform API API.
Redirect a user through the GO1 OAuth 2.0 authorisation code flow
Exchange an authorisation code for a bearer access token at the token endpoint
Retrieve the authenticated organisation account profile after sign-in
Bootstrap an OAuth client before calling the wider GO1 catalogue and enrolment endpoints
GET STARTED
Use for: I need to authenticate a user against GO1, Exchange an OAuth code for a GO1 access token, Get the GO1 account details for the authenticated user, Set up OAuth 2.0 with GO1 for a new integration
Not supported: Does not handle enrolments, course catalogue access, or SCORM packages — use for GO1 OAuth 2.0 sign-in and account verification only.
Jentic publishes the only available OpenAPI document for GO1 Learning Platform API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for GO1 Learning Platform API, keeping it validated and agent-ready. The GO1 Learning Platform API is a focused authentication and account-discovery surface for the GO1 online learning platform. It exposes the OAuth 2.0 authorisation code flow at /oauth/authorize and /oauth/token plus a single account endpoint that returns the authenticated organisation's profile. It is the lightweight entry point used by client applications before calling the broader GO1 v2 catalogue and enrolment endpoints.
Validate that an issued token belongs to the expected GO1 account before downstream calls
Patterns agents use GO1 Learning Platform API API for, with concrete tasks.
★ OAuth Bootstrap for Learning Apps
A learning application redirects users to /oauth/authorize, receives a code on the callback, and exchanges it at /oauth/token for a bearer access token. The app can then call /account to confirm which GO1 organisation the user belongs to before enrolling them in courses through the wider GO1 v2 API.
Open the GO1 authorisation URL, capture the code from the callback, exchange it for an access token, and call /account to record the organisation ID.
Account Verification Before Enrolment
Before issuing course enrolments, a workflow uses /account to confirm the connected GO1 organisation matches the customer's expected tenant. This prevents accidental cross-tenant enrolments when a single integration serves many GO1 customers.
Call /account with the user's bearer token and assert the returned organisation ID equals the customer's stored tenant ID.
AI Agent Sign-In Step
An AI agent that recommends GO1 courses needs a valid bearer token before calling enrolment endpoints. Through Jentic, the agent discovers and runs the OAuth exchange and account read as its first step, then chains into the broader GO1 v2 API for catalogue and enrolment work.
Search Jentic for 'go1 oauth token exchange', load the schema, run /oauth/token, and store the resulting bearer token for follow-up calls.
3 endpoints — jentic publishes the only available openapi specification for go1 learning platform api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/oauth/authorize
Start the OAuth 2.0 authorisation code flow
/oauth/token
Exchange a code for a bearer access token
/account
Retrieve the authenticated GO1 organisation account
/oauth/authorize
Start the OAuth 2.0 authorisation code flow
/oauth/token
Exchange a code for a bearer access token
/account
Retrieve the authenticated GO1 organisation account
Three things that make agents converge on Jentic-routed access.
Credential isolation
GO1 OAuth client IDs, secrets, and refresh tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive short-lived bearer tokens — raw secrets never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g. 'go1 oauth token exchange') and Jentic returns the right OAuth and account operations with their input schemas, so the agent can sign in without reading docs.
Time to first call
Direct GO1 OAuth integration: 1-2 days for redirect, callback, and token refresh handling. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
GO1 API
The wider GO1 v2 surface that handles enrolments, collections, and learning content.
Use this immediately after the Learning Platform API has produced a valid bearer token.
Udemy Business API
Udemy Business offers an alternative learning catalogue with its own auth flow.
Choose Udemy Business when the customer already runs Udemy; choose GO1 when they need a multi-vendor catalogue.
BambooHR API
BambooHR provides the employee identity that maps onto a GO1 learner record.
Pair BambooHR with GO1 when learner accounts must mirror HR-system records during onboarding.
Specific to using GO1 Learning Platform API API through Jentic.
Why is there no official OpenAPI spec for GO1 Learning Platform API?
GO1 publishes developer reference documentation but does not ship an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GO1 Learning Platform 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 GO1 Learning Platform API use?
It uses OAuth 2.0 with the authorisation code flow. Users hit /oauth/authorize, then the client exchanges the returned code at /oauth/token for a bearer access token. Jentic stores the client secret encrypted in the vault and handles token exchange on the agent's behalf.
Can I retrieve account details with the GO1 Learning Platform API?
Yes. GET /account returns the profile of the GO1 organisation associated with the bearer token, including identifiers needed before calling the wider GO1 v2 catalogue and enrolment endpoints.
What are the rate limits for the GO1 Learning Platform API?
The OpenAPI spec does not declare numeric rate limits. GO1 publishes plan-specific limits in its developer portal; in practice, this surface is hit infrequently because it only handles sign-in and account discovery.
How do I exchange an OAuth code for a GO1 token through Jentic?
Run a Jentic search for 'go1 oauth token exchange', load the schema for POST /oauth/token, and execute it with the authorisation code. Install with pip install jentic and use the async search, load, and execute pattern.
Should I use this API or the wider GO1 API?
Use the GO1 Learning Platform API for OAuth sign-in and account verification only. For course enrolments, learning objects, and collections, switch to the GO1 API at api.go1.com/v2 once you hold a valid bearer token.