1. Connect to Go1: 1.1 Connect customers via the Onboard API

2. Discover content: 2.1 Embed the Go1 catalogue component

3. Play content: 3.1 Download & play content as SCORM

4. Track learning: 4.1 Track learning via a native SCORM player

5. Manage content updates: 5.2 Content decommission webhook

3. Play content: 3.2 Play via authenticated play links

4. Track learning: 4.2 Track learning via webhooks

2. Discover content: 2.3 Build your own content catalogue interface (GraphQL)

Build your own catalogue UI & download SCORM via the API

1. Connect: 1.1 Setup a Go1 Portal and Author account

2. Author your content: 2.1 Author content using Go1 tools

3. Distribute your content: 3.1 Launch your content to market

4. Obtain insights: 4.1 Content insights dashboard

1. Connect: 1.2 API key setup & authentication

2. Author your content: 2.2 Author content via API integration

Use cases side menu

Twitter

LinkedIn

Youtube

Privacy

Customer Terms

Legal

Your Privacy Choices

DMCA

Accounting and Finance

Time Management

Sales and Customer Service

Digital Marketing

General Management

Housing and Real Estate

Human Resources

Industrial Skills

Investment and Trading

Leadership

Marketing

People and Communication Skills

Project Management

Business Skills

Language and Literature

Health and Well-being

Writing and Publishing

Audiovisual and Music

Personal Development

Health and Safety

HR Compliance

Data Compliance

Financial Compliance

Crisis Management

Safety and Compliance

IT Software

Web Design and Development

Data & Analytics

Design and Animation

Mobile App Development

Gaming and Games Development

Devops, Networking and Security

Programming and Web Development

Computer Science and Engineering

Technology Skills

World-class content

Seamless integrations

Why Go1

Small and midsize business

Enterprise

Solutions

Customer stories

Blog

Thought leadership

Events

Trust Center

Resources

Become a Distribution Partner

Become a Content Partner

Partners

About

Careers

Contact

Company

Integrate with Go1, using the Go1 Player

Developer Use case | Integrate with Go1, using the Go1 Player

In order to interact with the Go1 API and begin building your integration, you will need the following:

a Go1 account - a login to Go1 via email and password

a set of partner API keys - comprising of client_id, client_secret, and callback_url

A Go1 Implementation Manager will create your Go1 account, for which you will receive a welcome email, with instructions on how to set a password. They will also supply you with your partner API keys and a Partner portal ID. If you have not received these, reach out to your Implementation Manager or contact us to have one assigned. 

1. Set up your partner account

Each customer that uses your integration will require a ‘connected account’ for you to retrieve and play Go1 content. A ‘connected account’ means the customer has authorized you to access their Go1 resources using a ‘portal’ object via the Go1 API.

In this step, we’ll explore how connected accounts (portals) are created, and how a customer grants authorization for you to access Go1 resources through the API on their behalf.

There are two options for creating accounts with Go1. 

1. Standard (via OAuth) - the Go1 account (or portal) is created and controlled directly by the customer inside of your platform. For example, you might provide a 'Connect with Go1' button, which launches the Go1 account creation form. This is the fastest and easiest way to get started as Go1 simply manages the account creation process for you.

2. Custom (via API) - a customer's Go1 account is almost completely invisible to them throughout the account creation process - the heavy lifting will be handled behind the scenes via the API. The custom connection process provides the most flexibility when creating a customer account, but also requires the most integration effort and is most suitable for platforms who want to control the entire user experience.

If you choose to create accounts via the API method, you will also need to make sure that current Go1 customers can also connect to your integration. To build for this use case, follow the guides outlined in our Connect a portal page.

In this use case, we will walk through how to use the Standard option, via OAuth. If you would like to use the Custom option (via API), follow the steps to Create a portal via API.

2. Create a customer portal

The first resource we will retrieve from the API and display to your customers is Go1 content. A piece of Go1 content is represented as a learning-object in the API.

The steps below will walk you through how to retrieve and display a learning-object via the API, and provide a way for customers to search and discover Go1 content from inside your platform.

Build your own content catalogue interface (using the REST API)

3. Search content

Once it's possible for customers to search Go1 content in your platform, you'll need a way for them to play the content. This section will walk through how to play Go1 content using the Go1 player.

Play content via authenticated play links

4. Play content

Since you are playing content using the Go1 player, you will need a way to capture the user's enrolment information, such as when a user has completed a course.

There are several ways to track and report on learning enrolments in Go1 — you can retrieve user learning records by making a call to the API, or set a webhook to notify you when a user completes content. Select the most relevant method for your integration.

1. Return enrolment records via the API - using this option, you can poll the Go1 API to return enrolment records. You do this by making a GET request to https://api.go1.com/v2/enrollments.

There are a number of filtering options that you can implement, which allow you to segment the returned enrolment data. For example, you can return enrolments per user, per learning object, or filter by enrolment status (not started, in-progress, completed).

To use this option, reference the Enrolments API Documentation: (/v2/enrolments)

2. Track enrolments via the 'enrolment.update' webhook - by using a Go1 webhook, you can receive enrolment record updates for your users in real-time. The enrolment.update webhook delivers a payload for each enrollment creation, update, and completion.

To use this option, reference the Webhook API Documentation: (/v2/webhooks)

5. Retrieve enrolment records

This guide walks you through the process of building and launching your integration with Go1. Specifically, we'll illustrate how to connect new customers and get them searching and playing Go1 content inside your platform, using the Go1 player. 

You're done, great job! For more information or to see what else is possible with Go1, explore our concepts or API reference documentation.

curl --location --request GET 'https://api.go1.com/v2/learning-objects' \
--header 'Authorization: Bearer <CUSTOMER_ACCESS_TOKEN>'

{
    "total": 84315,
    "hits": [
		{
		    "id": LO ID,
		    "type": "LO TYPE (EG. COURSE)",
		    "title": "LO TITLE",
		    "image": "LO IMAGE URL",
		    "language": "en",
		    "description": "LO DESCRIPTION",
		    "created_time": "2019-03-16T09:28:21+00:00",
		    "updated_time": "2020-02-06T02:47:25+00:00",
		    "summary": "",
		    "assessable": true,
		    "collections": [],
		    "portal_collection": false,
		    "delivery": {
		        "duration": 12,
		        "mode": "self-paced"
		    },
		    "previewable": false,
		    "pricing": {
		        "currency": "AUD",
		        "price": 0,
		        "tax": 0,
		        "tax_included": true
		    },
		    "provider": {
		        "id": PROVIDER ID,
		        "logo": "PROVIDER LOGO IMAGE URL",
		        "name": "PROVIDER NAME"
		    },
		    "subscription": {
		        "licenses": -1,
		        "package": "premium"
		    },
		    "tags": [
		        "Writing",
		        "Creative Inspiration",
		        "Communication Skills"
		    ],
		    "attributes": {
		        //other attributes of the Learning Object; eg. topics, regional relevance, mobile compatibility, etc. 
		    }
		}
}

curl --location --request GET 'https://api.go1.com/v2/learning-objects?limit=50&offset=50' \
--header 'Authorization: Bearer <CUSTOMER_ACCESS_TOKEN>'

curl --location --request GET 'https://api.go1.com/v2/learning-objects?offset=0&limit=50&keyword=leadership&sort=relevance' \
--header 'Authorization: Bearer <CUSTOMER_ACCESS_TOKEN>'

curl --location --request GET 'https://api.go1.com/v2/learning-objects?keyword=leadership&sort=relevance' \
--header 'Authorization: Bearer <CUSTOMER_ACCESS_TOKEN>'

curl --location --request GET 'https://api.go1.com/v2/learning-objects?keyword=leadership&sort=popularity' \
--header 'Authorization: Bearer <CUSTOMER_ACCESS_TOKEN>'

curl --location -g --request POST 'https://api.go1.com/v2/users/<user-id>/login?redirect_url=/play/<lo-id>'
--header 'Authorization: Bearer <CUSTOMER-ACCESS-TOKEN>' \