GO1 Learning Platform API

Name: GO1 Learning Platform API
Brand: GO1 Learning Platform API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationLmsoauth23 EndpointsREST

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.

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

Install Jentic One Beta

Connect the GO1 Learning Platform API to your agent

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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%2Flearning-platform-api" | sh

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%2Flearning-platform-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 GO1 Learning Platform 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

Start building with GO1 Learning Platform API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GO1 Learning Platform 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.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for go1 learning platform api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/oauth/authorize

Start the OAuth 2.0 authorisation code flow

POST

/oauth/token

Exchange a code for a bearer access token

GET

/account

Retrieve the authenticated GO1 organisation account

GET

/oauth/authorize

Start the OAuth 2.0 authorisation code flow

POST

/oauth/token

Exchange a code for a bearer access token

GET

/account

Retrieve the authenticated GO1 organisation account

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the GO1 Learning Platform API by hand means running its OAuth2 authorize and token exchange against its auth host and verifying the account yourself. Through Jentic you install once, import the GO1 Learning Platform API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

This API covers OAuth2 sign-in and account verification, so scope the agent to the operations it needs, such as the token exchange and account read. You choose that operation set, so it signs in and verifies the account without any unrelated calls.

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 Jentic by intent such as 'GO1 OAuth token exchange' or 'verify a GO1 account', and Jentic returns the matching operation with its input schema so the agent signs in without reading the docs.

FAQs

Specific to using GO1 Learning Platform 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the GO1 Learning Platform API?

Yes. Because Jentic One is self-hosted, you decide which of this API's operations the agent may call and which credentials it may use. This API only covers OAuth 2.0 sign-in and account verification, so you can scope the agent to just the token exchange at /oauth/token and the account read at /account. That keeps it to signing in and confirming the organisation without any unrelated calls.