Agent-ready OpenAPI document · curated by JenticEducationLmsbearer, oauth234 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage GO1 learners, enrol them in learning objects, and add or remove items from collections. Useful for HR agents that automate compliance training rollouts.
Use for: I need to enrol a new hire in the GO1 onboarding course, Add a course to an existing GO1 collection, Get the SCORM package for a GO1 learning object, List all enrolments for a GO1 user
Not supported: Does not handle course authoring, video hosting, or live instructor-led training - use for managing GO1 enrolments, collections, and learning objects only.
Jentic publishes the only available OpenAPI specification for GO1 API, keeping it validated and agent-ready. The GO1 API is the v2 platform interface for the GO1 online learning marketplace, exposing OAuth client management, account information, learning collections, enrolments, learning objects (including SCORM packages), and SAML configuration. It is the preferred integration surface for embedding GO1 courses into an LMS or building AI-driven learning experiences that recommend, enrol, and report on training. Authentication is OAuth 2.0 with bearer tokens used for subsequent API calls.
Install Jentic One Beta
Connect the GO1 API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GO1 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgo1.com%2Fgo1-api" | 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%2Fgo1-api" | 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 GO1 API.
Authorise an OAuth client and exchange the code for a bearer access token
Enrol a user in a specific learning object and check the enrolment status
Add or remove learning objects from a curated collection
Retrieve a learning object including its SCORM package URL for embedding in an LMS
Manage staff client credentials for partner integrations
Configure SAML custom attribute mappings for SSO-driven learner provisioning
Use Cases
Patterns agents use GO1 API for, with concrete tasks.
★ Compliance Training Rollout
When an organisation rolls out mandatory compliance training, HR systems call the GO1 API to enrol every employee in a learning object and track completion. The /enrolments endpoint creates and reads enrolment records, while /learning-objects exposes course metadata and the SCORM package needed to render the content inside an LMS.
Enrol every user in department 'Engineering' into the data-protection learning object and report completion 30 days later.
Curated Learning Paths
Learning and Development teams build curated collections of GO1 courses for specific roles. The /collections/{collection-id}/items/add and /remove endpoints let an agent assemble or update a collection programmatically as new courses are published or retired.
Add the three newest leadership courses to collection 'Manager Onboarding' and remove courses flagged as deprecated.
SSO and Partner Provisioning
Partners that resell GO1 content provision learners via SAML SSO. The /saml/custom_attribute and /staff/client endpoints let an integration map identity attributes from the partner IdP to GO1 user records and manage the OAuth clients that downstream apps use.
Create a SAML custom attribute mapping for 'employee_id' on the partner's GO1 staff client.
AI Agent Skill Recommendation
An AI agent uses Jentic to recommend GO1 courses based on a learner's role and skill gaps. The agent searches for the enrolment operation, loads its schema, and chains it with /learning-objects lookups so the recommendation translates directly into an enrolment without leaving the chat surface.
Search Jentic for 'enrol go1 user', load the schema, and enrol the learner in the top three matching learning objects.
Key Endpoints
34 endpoints — jentic publishes the only available openapi specification for go1 api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/oauth/token
Exchange credentials for a bearer access token
GET
/account
Retrieve the authenticated organisation account
GET
/enrolments
List enrolment records
GET
/enrolments/{enrolment-id}
Get a specific enrolment by ID
GET
/learning-objects
List learning objects available to the account
GET
/learning-objects/{lo-id}/scorm
Fetch the SCORM package for a learning object
POST
/collections/{collection-id}/items/add
Add a learning object to a collection
POST
/collections/{collection-id}/items/remove
Remove a learning object from a collection
POST
/oauth/token
Exchange credentials for a bearer access token
GET
/account
Retrieve the authenticated organisation account
GET
/enrolments
List enrolment records
GET
/enrolments/{enrolment-id}
Get a specific enrolment by ID
GET
/learning-objects
List learning objects available to the account
GET
/learning-objects/{lo-id}/scorm
Fetch the SCORM package for a learning object
POST
/collections/{collection-id}/items/add
Add a learning object to a collection
POST
/collections/{collection-id}/items/remove
Remove a learning object from a collection
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
G
GO1 API
- Non-Ready (C)56/100
39
Foundational Compliance44
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability83
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
39
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
66%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
73%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
17%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
44
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: DSignals: 4
14%
Example Density
How richly the API is illustrated with examples.
98%
Example Validity
Percentage of examples that conform to their schemas.
62%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
0%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
54%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
85%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
83
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
82%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GO1 API by hand means running its OAuth2 flow alongside bearer auth, coordinating its API and auth hosts, and mapping the enrolment and collection endpoints yourself. Through Jentic you install once, import the GO1 API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
GO1 puts the collection id in the URL path (/collections/{collection-id}/items/add), so a rule can pin your agent to one collection: it can add and remove items there and nothing else. You choose the operations it may call, so it reads enrolments and learning objects only when you include those operations.
Credential isolation
Your GO1 OAuth client 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 'enrol a GO1 user' or 'add a learning object to a collection', and Jentic returns the matching GO1 operation with its input schema so the agent calls the right endpoint without browsing the developer docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using GO1 API through Jentic.
Why is there no official OpenAPI spec for GO1 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 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 API use?
GO1 uses OAuth 2.0 to issue access tokens at /oauth/token, then bearer tokens for subsequent calls. Jentic stores the OAuth client secret and refresh token encrypted in the vault and rotates the access token automatically before each call.
Can I enrol a user with the GO1 API?
Yes. POST /enrolments creates a new enrolment record for a user against a learning object, and GET /enrolments/{enrolment-id} returns the status. Use these together to drive automated training rollouts.
What are the rate limits for the GO1 API?
The OpenAPI spec does not declare numeric rate limits. GO1 publishes plan-specific limits in its developer portal; in practice, paginate list endpoints and back off on HTTP 429 responses.
How do I add a course to a GO1 collection through Jentic?
Run a Jentic search for 'add course to go1 collection', load the schema for POST /collections/{collection-id}/items/add, and execute it with the learning object ID. Install with pip install jentic and chain search, load, and execute.
Does the GO1 API support SCORM packages?
Yes. GET /learning-objects/{lo-id}/scorm returns the SCORM package URL for a learning object so it can be launched inside an external LMS.
Can I limit what my agent is allowed to do with the GO1 API?
Yes. Because you run Jentic One yourself, your own rules decide which GO1 operations and credentials the agent may use. Since the collection id sits in the URL path at /collections/{collection-id}/items/add, you can pin the agent to a single collection so it only adds and removes items there and touches nothing else. You choose the operations it may call, so it reads enrolments and learning objects only when you include those endpoints.
GET STARTED