Getting started with the Skilljar API

API Keys and Authentication

API Key

API keys are generated via the Skilljar Dashboard. If you are an admin on your account, you can generate an API Key from Organization settings > API Credentials page. Select the "Create a Key" button to generate a new API Key. You can use this API key to begin making a few basic API calls.

Skilljar's API endpoint is https://api.skilljar.com/v1

Note: You can create read-only API keys to grant partners safe, view-only access.

Authentication

API calls are authenticated via HTTP Basic Authentication. The API Key is the User, and the password is blank. For example, if your key is "sk-live-abcdeg", then all requests to our API endpoint should contain the HTTP Header:

Authorization: Basic c2stbGl2ZS1hYmNkZWc6

That is, where c2stbGl2ZS1hYmNkZWc6 is the base-64 encoded string sk-live-abcdeg: as per the HTTP Basic Auth spec. Most HTTP libraries will do this for you, so you don't have to worry about constructing and adding the header explicitly.

Alternatively, you can pass in API key in the user field: --user ""

First API call - Ping the API endpoint

You can test a basic call & response via making an HTTP GET request to our "ping" endpoint:

https://api.skilljar.com/v1/ping

A successfully authenticated request should return an empty 200 response.

You'll notice if you access the/ping endpoint in your browser (and paste in your API key in the username prompt), you'll see a full HTML page with the API response. All of our APIs are accessible in this way to facilitate debugging.

JSON

To communicate with our endpoint using JSON encoding, you will want to specify it the Accept: header in your HTTP request. This doesn't apply much to the /ping endpoint since there is an empty response, but will apply once you start making legitimate API calls:

Accept: application/json

API Resource Reference

There are a few main resources within the Skilljar API. REST-like manipulation of these resources allow you to manage users within the course platform, enroll users in courses, and receive event notifications from the platform.

Domain

This is the domain your courses are hosted on, e.g., courses.yoursite.com

User

Auseris a student within the system.

Course

This is a course.

PublishedCourse

A course is published to a domain via a PublishedCourse object

DomainUser

A user has access to a domain via a DomainUser object

Enrollment

A user is enrolled in a PublishedCourse via an Enrollment object.

Webhook

You can be notified of events within the course platform via Webhook objects.

In addition to core resources, you can now programmatically manage content objects such as Catalog Pages, Published Courses, Published Paths, and Assessments. Refer to the Content Management API section.

The Details - API Endpoint Reference

Now that you understand how to make an API call, and what the primary resources are within the system, it's time to browse the API Endpoint Reference. The reference lives on your API endpoint and is generated dynamically from the source code itself. It's always up-to-date with the latest details about the platform.

The article Common API Tasks outlines some common uses of the Skilljar API and gives examples of using the API to create users, enroll them in courses, add them to domains, etc. You can also use our Webhooks API to listen for events that happen within Skilljar.

Try it out!

Navigate to https://api.skilljar.com/docs/
To test a specific API call, click on the "Try it out!" button
You'll be prompted for your Username and Password
In the Username field, enter in the API Key obtained to the Skilljar Dashboard
Leave the Password field blank and click the "Sign In" button:

Content Management API

With the help of API, you can efficiently manage training content, automate key processes, and enhance learner experiences. This integration streamlines the management of courses, learning paths, catalog pages, assessments, and supplemental resources.

You can manage the content by using the following endpoints and fields:

Assets

Delete an asset using the endpoint:DELETE /v1/assets/{asset_id}.

Courses

Manage and organise the content of courses using the following endpoints:

Actions	End-points
CRUD supoport for Labels	GET /v1/courses/{course_id}/labels POST /v1/courses/{course_id}/labels DELETE /v1/courses/{course_id}/labels/{label_id}
Delete a course	DELETE /v1/courses/{course_id}
Create new filter	?label__name= and ?course__id= as

The API also returns the following metadata:

draft_origin_id
promo_image_url
display_course_and_lesson_time
manual_course_time
display_manual_course_time
course_and_lesson_time_format
course_time
created_at
modified_at

Published

The section provides the API endpoints for published courses and paths.

Published Courses

The following endpoints are available to manage published courses:

Actions	Endpoints
CRUD support for published courses	POST /v1/domains/{domain_name}/published-courses PUT /v1/domains/{domain_name}/published-courses/{published_course_id} PATCH /v1/domains/{domain_name}/published-courses/{published_course_id} DELETE /v1/domains/{domain_name}/published-courses/{published_course_id}
Create new filter	Use ?course__id=abc123 endpoint on the list published courses.
Manage prerequisites	/published-course-prerequisites
Set reenrollment rules	/reenrollment_rule
Add student group prerequisites	/student-group-prerequisites
Manage tags	/tags
Control visibility overrides	/visibility-overrides

Published Paths

The following endpoints are available to manage published paths:

Actions	Endpoints
CRUD support for Published paths	Use POST, PUT, PATCH, DELETE on /published-paths
Labels	/labels
Tags	/tags
Overrides	/visibility-overrides
Create new filter	?label__name= and ?course__id= as

In addition to the endpoints, the API also returns the following metadata to manage your catalog:

slug
created_at
modified_at
promo_image_url

Organise

Organise the existing contents for the following catalog:

Content	Description
Catalog Pages	CRUD support through /catalog-pages endpoint. Classic page items support through /classic-page-items endpoint.
Labels	CRUD support for the labels using /labels endpoint.
License Package Seats	You can add or update students in license packages using the following: GET /v1/license-packages/{license_package_id}/students POST /v1/license-packages/{license_package_id}/students PUT /v1/license-packages/{license_package_id}/students PATCH /v1/license-packages/{license_package_id}/students
Tags	CRUD support using /tags endpoints.
Lessons	Delete lessons DELETE /v1/lessons/ {id}
Paths	To update paths, use the following endpoints: PUT /v1/paths/{path_id} PATCH /v1/paths/{path_id} The new fields are also available to manage paths: promo_image_url short_description long_description_html header_html course_name_singular
Question Banks	To delete using DELETE /v1/question-banks/{question_bank_id} endpoint. To manage question bank use /questions endpoint.
Quizzes	To delete using DELETE /v1/question-banks/quizzes/{quizz_id} endpoint. To manage use /questions endpoint.
Web package	To delete use DELETE /v1/web-packages/{id} endpoint.

API Call Rate Limits

We enforce the following API rate limits to ensure the highest levels of API availability and reliability.

Rate Limits are per Skilljar Organization (not per API key)
Rate limits are per call type
- Modification and Removal rate limits are separate from each other
Rate Limit Volumes
- Burst rates up to 600 API calls per minute
- Hourly rate up to 5,000 API calls per hour
  Note: API Call Rate Limits only apply to the External API endpoints found in our API documentation. SAML, OAuth, and OIDC calls do not use the same API endpoints.
Rate limit time frames reset depending on when the request is made.
Example: For the hour limit - if one request is made at 12:00 and 4,999 requests are made at 12.59, further requests cannot be made until the first request expires at 1:00, an hour after it was made. At 1:00 a new request can now be made, but any further requests will receive throttle responses until the other 4,999 expire at 1:59.

Rate Limit Error response:

If you hit one of the rate limits, the API response body will include the following information (among the rest of the API response)

'status_code': 429
'reason': 'Too Many Requests'

Read Only API Keys

What are Read-Only API Keys?

Read-only API keys are designed to permit only "Read" or "Get" operations. This feature allows you to enable Integration Partners to gather data from the Skilljar API without the risk of altering or modifying your learning site or data.

By granting read-only API keys, you can securely allow integration partners to access your data without the risk of them modifying any information and ensure that your downstream tools and applications have the precise level of access they need to your API data, without exposing your organization to unnecessary risks.

Implementation Details

Validation for Every API Operation: When a call is made, the system checks for key permission (new boolean) and denies any POST, PUT, UPDATE, DELETE requests if the key is read-only.
Dashboard Setting: This can be defined on the dashboard when creating API keys and cannot be edited once the key is saved.
- For more details and to create an API key, visit Skilljar API Key Creation.

Important Notes about Read-Only Keys

Some integrations may require write access (e.g., to create a webhook), so if a partner has already built an integration with Skilljar, ensure they are okay with only using a Read-Only key.
Once a read-only key has been generated, it is not possible to “edit” that key to be able to write. If you want to provide a full-access key to an integration partner, you can delete the “Read-Only” key and create a new normal key to pass securely to your integration partner. If an integration needs write access, for example, to create webhooks, use a standard API key instead.