Skilljar API endpoint reference

This page documents API endpoints supported by the Skilljar platform. It is auto-generated from our source code and therefore kept up to date as we add additional operations. To learn about the Skilljar API and get an overview of how objects are structured within the course platform, it's better to start with the following articles:

domains

list

GET /v1/domains

List domains. Returns a paginated response (100 results per page) of domains. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "name": "example.com", "catalog_title": "<h1 style=\"font-weight: 400; font-size: 28px;\">All Courses</h1>", "access": "PUBLIC", "access_code_message_html": "", "marketing_message": "" } ] }

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

read

GET /v1/domains/{domain_name}

Get domain details. Example Response: { "id": "abcdefg123456", "name": "example.com", "catalog_title": "<h1 style=\"font-weight: 400; font-size: 28px;\">All Courses</h1>", "private": true, "access": "PUBLIC", "access_code_message_html": "", "marketing_message": "" }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

update

PUT /v1/domains/{domain_name}

Update domain details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`catalog_title`	HTML content displayed at the top of the catalog page	`String`
`access`	Domain access settings	`Enum`
`access_code_message_html`		`String`
`marketing_message`	Private domain marketing opt-in message, shown with checkbox on the signup page	`String`

partial_update

PATCH /v1/domains/{domain_name}

Update domain details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`catalog_title`	HTML content displayed at the top of the catalog page	`String`
`access`	Domain access settings	`Enum`
`access_code_message_html`		`String`
`marketing_message`	Private domain marketing opt-in message, shown with checkbox on the signup page	`String`

access-code-pools > list

GET /v1/domains/{domain_name}/access-code-pools

List access code pools for a domain. Returns a paginated list (100 results per page) of access code pools.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`name`	Filter returned access code pools by name	`String`

access-code-pools > create

POST /v1/domains/{domain_name}/access-code-pools

Create an empty pool of domain access codes.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name` required	Name of the access code pool. This may have been auto-generated when creating individual codes in the dashboard.	`String`
`active`		`Boolean`
`start_date`		`String`
`end_date`		`String`
`expire_linked_to_domain_membership`	When this is true and an end_date is set, a user who registers with a code from this pool will lose access to the domain on the end_date.	`Boolean`

access-code-pools > read

GET /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}

Retrieve access code pool details. Example Response: { "id": "abcde1234", "name": "example-pool", "active": true, "start_date": 2016-01-29T00:22:00.590250Z, "end_date": null, "expire_linked_to_domain_membership": false, "channel": "api", "code_count": 1 }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`

access-code-pools > update

PUT /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}

Update access code pool. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name`	Name of the access code pool. This may have been auto-generated when creating individual codes in the dashboard.	`String`
`active`		`Boolean`
`start_date`		`String`
`end_date`		`String`
`expire_linked_to_domain_membership`	When this is true and an end_date is set, a user who registers with a code from this pool will lose access to the domain on the end_date.	`Boolean`

access-code-pools > partial_update

PATCH /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}

Update access code pool. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name`	Name of the access code pool. This may have been auto-generated when creating individual codes in the dashboard.	`String`
`active`		`Boolean`
`start_date`		`String`
`end_date`		`String`
`expire_linked_to_domain_membership`	When this is true and an end_date is set, a user who registers with a code from this pool will lose access to the domain on the end_date.	`Boolean`

access-code-pools > delete

DELETE /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}

Delete access code pool. This will delete all access codes in the pool.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`

access-code-pools > access-codes > list

GET /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}/access-codes

List access codes in a pool. Returns a paginated list (1000 results per page) of access codes. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcde12345", "code": "examplecode", "active": true, "max_uses": 3, "use_count": 2, "duration": null, "duration_unit": "MONTHS" } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

access-code-pools > access-codes > create

POST /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}/access-codes

Add an access code to a pool.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`code`		`String`
`active`		`Boolean`
`max_uses`		`Integer`
`duration`		`Integer`
`duration_unit`		`Enum`

access-code-pools > access-codes > read

GET /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}/access-codes/{access_code_id}

Retrieve access code details. Example Response: { "code": "examplecode", "active": true, "max_uses": 3, "use_count": 2, "duration": null, "duration_unit": "Months" "users": [ { "id": "abcdef12345", "email": "janedoe@example.com", "first_name": "Jane", "last_name": "Doe" }, { "id": "bcdeg23456", "email": "jamesdoe@example.com", "first_name": "James", "last_name": "Doe" }, ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`
`access_code_id` required		`String`

access-code-pools > access-codes > update

PUT /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}/access-codes/{access_code_id}

Update access code. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`
`access_code_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`code`		`String`
`active`		`Boolean`
`max_uses`		`Integer`
`duration`		`Integer`
`duration_unit`		`Enum`

access-code-pools > access-codes > partial_update

PATCH /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}/access-codes/{access_code_id}

Update access code. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`
`access_code_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`code`		`String`
`active`		`Boolean`
`max_uses`		`Integer`
`duration`		`Integer`
`duration_unit`		`Enum`

access-code-pools > access-codes > delete

DELETE /v1/domains/{domain_name}/access-code-pools/{access_code_pool_id}/access-codes/{access_code_id}

Delete access code.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`access_code_pool_id` required		`String`
`access_code_id` required		`String`

course-series > list

GET /v1/domains/{domain_name}/course-series

List course series on a domain.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

course-series > read

GET /v1/domains/{domain_name}/course-series/{course_series_id}

Retrieve course series details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`course_series_id` required		`String`

course-series > published-courses > list

GET /v1/domains/{domain_name}/course-series/{course_series_id}/published-courses

List published courses in a course series

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`course_series_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

plan > list

GET /v1/domains/{domain_name}/plan

Returns a list of Plans in a domain. Returns a paginated list (100 results per page) of Plans. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "plan": { "id": "cdefghi345678", "title": "Example Plan Title", }, "plan_url": "http://learn.example.com/plan/example-plan-title", "offer": { "id": "bcdefgh234567", "registration_open": true, "registration_url": "http://learn.example.com/checkout/bcdefgh234567", "price": { "amount": "20.00", "currency_code": "USD" } } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

plan > read

GET /v1/domains/{domain_name}/plan/{plan_id}

Retrieve Plan details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`plan_id` required		`String`

plan > plan-enrollments > list

GET /v1/domains/{domain_name}/plan/{plan_id}/plan-enrollments

List enrollments for a Plan. A user may have multiple plan enrollments, and will have access to a plan if at least one of the enrollments is active and not expired. If an enrollment was created in association with a purchase, or registration through the course platform UI, the purchase details are included in the response. Returns a paginated list (1000 results per page) of enrollments. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "user": { "id": "bcdefga123456", "email": "jane@doe.com", "first_name": "Jane", "last_name": "Doe", }, "enrolled_at": "2015-01-29T00:22:00.590250Z", "expires_at": null, "active": true, "purchase": { "order_id": "", "offer_price": { "amount": "100.00", "currency_code": "USD" }, "purchase_price": { "amount": "50.00", "currency_code": "USD" }, "quantity": 1, "purchase_state": "SUCCESS", "payment_processor": "STRIPE", "purchase_id": "xxxxxxxxxxxx", "purchased_at": "2020-08-19T14:12:25.736506Z", "tax_price_cents": 0 } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`plan_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

plan > plan-enrollments > create

POST /v1/domains/{domain_name}/plan/{plan_id}/plan-enrollments

Enroll a user in a Plan. This operation is idempotent on the user.id & enrolled_at combination. POSTing multiple times to this endpoint will NOT create a new enrollment for an existing user.id & enrolled_at combination. However, each call will create a new enrollment if either the user.id or enrolled_at parameter does not match an existing enrollment. purchase_state = 'CREATED', 'PENDING', 'SUCCESS', 'FAILED', 'REFUNDED', 'CANCELLED', or 'FLAGGED' Example POST body (if POSTing JSON rather than form-encoded parameters): { "user": { "id": "abcde12345", }, "enrolled_at" : "2018-03-12T10:12:45Z", "expires_at" : "2018-05-12T10:12:45Z", "active": true, "purchase": { "purchase_state": "SUCCESS", "purchase_price": { "amount": "5.00", "currency_code": "USD" }, "purchased_at": "2018-02-12T10:12:45Z", "tax_price_cents": 100 } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`plan_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`user` required		`Object`
`enrolled_at`		`String`
`expires_at`		`String`
`active`		`Boolean`
`purchase`		`Object`

plan > plan-enrollments > read

GET /v1/domains/{domain_name}/plan/{plan_id}/plan-enrollments/{plan_enrollment_id}

Get Plan enrollment details. If an enrollment was created in association with a purchase, or registration through the course platform UI, the purchase details are included in the response.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`plan_id` required		`String`
`plan_enrollment_id` required		`String`

plan > plan-enrollments > update

PUT /v1/domains/{domain_name}/plan/{plan_id}/plan-enrollments/{plan_enrollment_id}

Update enrollment details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`plan_id` required		`String`
`plan_enrollment_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`expires_at`		`String`
`active`		`Boolean`

plan > plan-enrollments > partial_update

PATCH /v1/domains/{domain_name}/plan/{plan_id}/plan-enrollments/{plan_enrollment_id}

Update enrollment details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`plan_id` required		`String`
`plan_enrollment_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`expires_at`		`String`
`active`		`Boolean`

published-courses > list

GET /v1/domains/{domain_name}/published-courses

List courses published to a domain. Returns a paginated list (100 results per page) of published courses. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "course": { "id": "cdefghi345678", "title": "Example Title" }, "slug": "example-course", "course_url": "http://learn.example.com/example-course", "hidden": false, "registration_required": true, "registration_starts_at": "2017-11-28T08:00:00Z", "registration_ends_at": "2018-09-30T06:00:00Z", "timezone": "US/Pacific", "offer": { "id": "bcdefgh234567", "registration_open": true, "registration_url": "http://learn.example.com/checkout/bcdefgh234567", "price": { "amount": "100.00", "currency_code": "USD" } } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`include_searchable_content`	If set to True, the response also includes the following fields ('lesson_list', 'tags', 'short_description', 'long_description_html', 'search_keywords')	`String`
`search`	URL encoded string, return the results and the order as if a catalog search	`String`

published-courses > read

GET /v1/domains/{domain_name}/published-courses/{published_course_id}

Retrieve course details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_course_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`include_searchable_content`	If set to True, the response also includes the following fields ('lesson_list', 'tags', 'short_description', 'long_description_html', 'search_keywords')	`String`

published-courses > enrollments > list

GET /v1/domains/{domain_name}/published-courses/{published_course_id}/enrollments

List enrollments for a PublishedCourse. A user may have multiple enrollments, and will have access to a course if at least one of the enrollments is active and not expired. If an enrollment was created in association with a purchase, or registration through the course platform UI, the purchase details are included in the response. Returns a paginated list (1000 results per page) of enrollments. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "user": { "id": "bcdefga123456", "email": "jane@doe.com", "first_name": "Jane", "last_name": "Doe", }, "enrolled_at": "2015-01-29T00:22:00.590250Z", "expires_at": null, "active": true, "purchase": { "order_id": "", "offer_price": { "amount": "100.00", "currency_code": "USD" }, "purchase_price": { "amount": "50.00", "currency_code": "USD" }, "quantity": 1, "purchase_state": "SUCCESS", "payment_processor": "STRIPE", "purchase_id": "xxxxxxxxxxxx", "purchased_at": "2021-07-02T18:17:30.640768Z", "tax_price_cents": 0 } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_course_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

published-courses > enrollments > create

POST /v1/domains/{domain_name}/published-courses/{published_course_id}/enrollments

Enroll a user in a PublishedCourse. This operation is idempotent on the user.id & enrolled_at combination. POSTing multiple times to this endpoint will NOT create a new enrollment for an existing user.id & enrolled_at combination. However, each call will create a new enrollment if either the user.id or enrolled_at parameter does not match an existing enrollment. purchase_state = 'CREATED', 'PENDING', 'SUCCESS', 'FAILED', 'REFUNDED', 'CANCELLED', or 'FLAGGED' Example POST body (if POSTing JSON rather than form-encoded parameters): { "user": { "id": "abcde12345", }, "enrolled_at" : "2018-03-12T10:12:45Z", "expires_at" : "2018-05-12T10:12:45Z", "active": true, "purchase": { "purchase_state": "SUCCESS", "purchase_price": { "amount": "5.00", "currency_code": "USD" }, "purchased_at": "2018-02-12T10:12:45Z", "tax_price_cents": 100 } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_course_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`user` required		`Object`
`enrolled_at`		`String`
`expires_at`		`String`
`active`		`Boolean`
`purchase`		`Object`

published-courses > enrollments > read

GET /v1/domains/{domain_name}/published-courses/{published_course_id}/enrollments/{enrollment_id}

Get enrollment details. If an enrollment was created in association with a purchase, or registration through the course platform UI, the purchase details are included in the response.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_course_id` required		`String`
`enrollment_id` required		`String`

published-courses > enrollments > update

PUT /v1/domains/{domain_name}/published-courses/{published_course_id}/enrollments/{enrollment_id}

Update enrollment details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_course_id` required		`String`
`enrollment_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`expires_at`		`String`
`active`		`Boolean`

published-courses > enrollments > partial_update

PATCH /v1/domains/{domain_name}/published-courses/{published_course_id}/enrollments/{enrollment_id}

Update enrollment details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_course_id` required		`String`
`enrollment_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`expires_at`		`String`
`active`		`Boolean`

published-paths > list

GET /v1/domains/{domain_name}/published-paths

Returns a list of Published Paths published to a domain. Returns a paginated list (100 results per page) of Published Paths. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "path": { "id": "cdefghi345678", "title": "Example Path Title", "path_item_count": 0 }, "path_url": "http://learn.example.com/path/example-path-title", "offer": { "id": "bcdefgh234567", "registration_open": true, "registration_url": "http://learn.example.com/checkout/bcdefgh234567", "price": { "amount": "20.00", "currency_code": "USD" } } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

published-paths > read

GET /v1/domains/{domain_name}/published-paths/{id}

Retrieve Published Path details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`id` required		`String`

published-paths > published-path-enrollments > list

GET /v1/domains/{domain_name}/published-paths/{published_path_id}/published-path-enrollments

List enrollments for a Published Path. A user may have multiple published path enrollments, and will have access to a path if at least one of the enrollments is active and not expired. If an enrollment was created in association with a purchase, or registration through the course platform UI, the purchase details are included in the response. Returns a paginated list (1000 results per page) of enrollments. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcdefg123456", "user": { "id": "bcdefga123456", "email": "jane@doe.com", "first_name": "Jane", "last_name": "Doe", }, "enrolled_at": "2015-01-29T00:22:00.590250Z", "expires_at": null, "active": true, "purchase": { "order_id": "", "offer_price": { "amount": "100.00", "currency_code": "USD" }, "purchase_price": { "amount": "50.00", "currency_code": "USD" }, "quantity": 1, "purchase_state": "SUCCESS", "payment_processor": "STRIPE", "purchase_id": "xxxxxxxxxxxx", "purchased_at": "2021-07-02T18:17:30.640768Z", "tax_price_cents": 0 } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_path_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

published-paths > published-path-enrollments > create

POST /v1/domains/{domain_name}/published-paths/{published_path_id}/published-path-enrollments

Enroll a user in a PublishedPath. This operation is idempotent on the user.id & enrolled_at combination. POSTing multiple times to this endpoint will NOT create a new enrollment for an existing user.id & enrolled_at combination. However, each call will create a new enrollment if either the user.id or enrolled_at parameter does not match an existing enrollment. purchase_state = 'CREATED', 'PENDING', 'SUCCESS', 'FAILED', 'REFUNDED', 'CANCELLED', or 'FLAGGED' Example POST body (if POSTing JSON rather than form-encoded parameters): { "user": { "id": "abcde12345", }, "enrolled_at" : "2018-03-12T10:12:45Z", "expires_at" : "2018-05-12T10:12:45Z", "active": true, "purchase": { "purchase_state": "SUCCESS", "purchase_price": { "amount": "5.00", "currency_code": "USD" }, "purchased_at": "2018-02-12T10:12:45Z", "tax_price_cents": 100 } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_path_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`user` required		`Object`
`enrolled_at`		`String`
`expires_at`		`String`
`active`		`Boolean`
`purchase`		`Object`

published-paths > published-path-enrollments > read

GET /v1/domains/{domain_name}/published-paths/{published_path_id}/published-path-enrollments/{published_path_enrollment_id}

Get Published Path enrollment details. If an enrollment was created in association with a purchase, or registration through the course platform UI, the purchase details are included in the response.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_path_id` required		`String`
`published_path_enrollment_id` required		`String`

published-paths > published-path-enrollments > update

PUT /v1/domains/{domain_name}/published-paths/{published_path_id}/published-path-enrollments/{published_path_enrollment_id}

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_path_id` required		`String`
`published_path_enrollment_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`expires_at`		`String`
`active`		`Boolean`

published-paths > published-path-enrollments > partial_update

PATCH /v1/domains/{domain_name}/published-paths/{published_path_id}/published-path-enrollments/{published_path_enrollment_id}

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`published_path_id` required		`String`
`published_path_enrollment_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`expires_at`		`String`
`active`		`Boolean`

GET /v1/domains/{domain_name}/signup-fields

List signup fields for a domain.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

users > list

GET /v1/domains/{domain_name}/users

List users for a domain. Returns a paginated list (1000 results per page) of domain user details. Example Response: { "count": 2, "next": null, "previous": null, "results": [ { "user": { "id": "opqrstu345678", "email": "joe@example.com", "first_name": "Joe", "last_name": "User" }, "active": true, "marketing_optin": null, "enrolled_at": "2015-01-29T00:22:00.590250Z", "expires_at": null, "access_code": null }, { "user": { "id": "cdefghi567890", "email": "jane@example.com", "first_name": "Jane", "last_name": "Doe" }, "active": false, "marketing_optin": null, "enrolled_at": "2015-02-15T00:43:10.123456Z", "expires_at": null, "access_code": { "id": "defghij678901", "code": "opensesame", "pool": { "id": "efghijk789012", "name": "Genie Codes" } } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`user__email`	Filter domain users by email address	`String`
`user__first_name`	Filter domain users by first name - case sensitive	`String`
`user__last_name`	Filter domain users by last name - case sensitive	`String`
`active`	Filter domain users by active (true or false)	`String`
`access_code__code`	Filter domain users by access code used - case sensitive	`String`
`access_code__id`	Filter domain users by id of access code used - not case sensitive	`String`
`access_code__pool__id`	Filter domain users by id of access code pool used - not case sensitive	`String`
`access_code`	Use a value of "null" to see domain users who accessed the domain without an access code. No other values are accepted for this query.	`String`

users > create

POST /v1/domains/{domain_name}/users

Add a user to a domain. Users must have unique email addresses. You may POST an existing user (existing email address) to the domain, and the call will still return successfully with the existing user details. If you POST a new user email to the domain, the call will create a new user within the system. Example POST body (if POSTing JSON rather than form-encoded parameters): { "user": { "email": "bob@example.com", "first_name": "Bob", "last_name": "User" } } Example Response: { "user": { "id": "qrstuvw321098", "email": "bob@example.com", "first_name": "Bob", "last_name": "User" }, "active": true, "marketing_optin": null, "enrolled_at": "2015-01-29T00:22:00.590250Z", "expires_at": null, "access_code": null, "login_token": "qrstuvw321098-3xn-a1b23cd456dfg7890hijk" }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`user` required	User details	`Object`
`active`	Only active users have access to a private domain	`Boolean`
`marketing_optin`	Indicates user has accepted or rejected the marketing optin message. Null indicates no marketing option message was shown to user	`Boolean`
`expires_at`	ISO 8601 formatted datetime string indicating when the access to the domain will expire - ignored on public domains	`String`

users > read

GET /v1/domains/{domain_name}/users/{user_id}

Get details about a user on a domain.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

users > update

PUT /v1/domains/{domain_name}/users/{user_id}

Update domain user. Only active and expires_at may be updated. Access codes may also be removed by setting the entire access_code to null. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`active`		`Boolean`
`expires_at`		`String`
`access_code`	Information about the access code entered by the user, if they used one to join a private domain	`Object`

users > partial_update

PATCH /v1/domains/{domain_name}/users/{user_id}

Update domain user. Only active and expires_at may be updated. Access codes may also be removed by setting the entire access_code to null. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`active`		`Boolean`
`expires_at`		`String`
`access_code`	Information about the access code entered by the user, if they used one to join a private domain	`Object`

users > invites > list

GET /v1/domains/{domain_name}/users/{user_id}/invites

List all invites for a user on this domain

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

users > invites > create

POST /v1/domains/{domain_name}/users/{user_id}/invites

Create domain user invite. This will send the user an invitation via email unless send_email is set to False. User must have already been added to the domain. ---

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`send_email`	Whether or not to send the user an email inviting them to the domain. Defaults to True	`Boolean`

users > invites > read

GET /v1/domains/{domain_name}/users/{user_id}/invites/{domain_user_invite_id}

Get domain user invite details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`
`domain_user_invite_id` required		`String`

GET /v1/domains/{domain_name}/users/{user_id}/signup-fields

List a user's signup fields.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

POST /v1/domains/{domain_name}/users/{user_id}/signup-fields

Create or update a user's signup field value. If the user does not have a current value assigned to the POSTed signup field, this endpoint will create a new signup field value for the user. If the user already has a value associated with the signup field, it will be updated to the POSTed value. Example POST body (if POSTing JSON rather than form-encoded parameters): { "signup_field": { "id": "abcd1234" }, "value": "My Signupfield Value" }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`signup_field` required		`Object`
`value` required		`String`

GET /v1/domains/{domain_name}/users/{user_id}/signup-fields/{signup_field_id}

View a user's signup field value.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`domain_name` required		`String`
`user_id` required		`String`
`signup_field_id` required		`String`

groups

list

GET /v1/groups

List groups. Returns a paginated list (1000 results per page) of groups. name -- filter groups by exact match on group name

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`name`	Filter groups by exact match on group name	`String`

create

POST /v1/groups

Create a group.

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name` required	Unique name of the group	`String`

read

GET /v1/groups/{group_id}

Get group details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

update

PUT /v1/groups/{group_id}

Update group details. Currently you may only change the name of the group. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name` required	Unique name of the group	`String`

partial_update

PATCH /v1/groups/{group_id}

Update group details. Currently you may only change the name of the group. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name`	Unique name of the group	`String`

delete

DELETE /v1/groups/{group_id}

Delete group. Completely removes the Group and all GroupUsers. Users and DomainUsers are preserved. This operation cannot be undone.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

access-code-pools > list

GET /v1/groups/{group_id}/access-code-pools

List access code pools for a group. Returns a paginated list (1000 results per page) of access code pool details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

access-code-pools > create

POST /v1/groups/{group_id}/access-code-pools

Add an access code pool to a group. Example POST body (if POSTing JSON rather than form-encoded parameters): { "access_code_pool": { "id": "abcde12345", } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`access_code_pool` required		`Object`

access-code-pools > read

GET /v1/groups/{group_id}/access-code-pools/{access_code_pool_id}

Get details about an access code pool in a group.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`
`access_code_pool_id` required		`String`

access-code-pools > delete

DELETE /v1/groups/{group_id}/access-code-pools/{access_code_pool_id}

Remove an access code pool from a group.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`
`access_code_pool_id` required		`String`

users > list

GET /v1/groups/{group_id}/users

List users in a group. Returns a paginated list (1000 results per page) of group user details. Example Response: { "count": 2, "next": null, "previous": null, "results": [ { "user": { "id": "opqrstu345678", "email": "joe@example.com", "first_name": "Joe", "last_name": "User" }, "created_at": "2015-02-19T19:20:24.671362Z" }, { "user": { "id": "cdefghi567890", "email": "jane@example.com", "first_name": "Jane", "last_name": "Doe" }, "created_at": "2015-02-18T10:37:48.543927Z" } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

users > create

POST /v1/groups/{group_id}/users

Add a user to a group. Example POST body (if POSTing JSON rather than form-encoded parameters): { "user": { "id": "abcde12345", } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`user` required	User details	`Object`

users > read

GET /v1/groups/{group_id}/users/{user_id}

Get details about a user in a group.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`
`user_id` required		`String`

users > delete

DELETE /v1/groups/{group_id}/users/{user_id}

Remove a user from a group.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`group_id` required		`String`
`user_id` required		`String`

lesson-progress

read

GET /v1/lesson-progress/{lesson_progress_id}

Get lesson progress details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`lesson_progress_id` required		`String`

update

PUT /v1/lesson-progress/{lesson_progress_id}

Update for lesson progress. PUT and PATCH are identical - both do partial updates. Setting finished_at indicates that the student has finished the content. This will also mark the lesson complete unless the lesson requires validation, such as a review of proctoring. To un-complete the lesson, set completed_at to null.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`lesson_progress_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`finished_at`	ISO 8601 formatted datetime string indicating when the user finished the lesson content. Setting this field will also mark the lesson complete unless the lesson requires validation, such as a review of proctoring.	`String`
`completed_at`	ISO 8601 formatted datetime string indicating when the user completed the lesson. If null, the user has not completed the lesson.	`String`
`success_status`	'PASSED', 'FAILED' or null	`Enum`
`score`	Score received	`Integer`
`max_score`	Max possible score	`Integer`
`custom_data`		`String`
`validation_status`	'PASSED', 'FAILED' or null	`Enum`
`validation_data`	JSON formatted. Ignored if the lesson does not require validation.	`Object`

partial_update

PATCH /v1/lesson-progress/{lesson_progress_id}

Partial update for lesson progress. PUT and PATCH are identical - both do partial updates. Setting finished_at indicates that the student has finished the content. This will also mark the lesson complete unless the lesson requires validation, such as a review of proctoring. To un-complete the lesson, set completed_at to null.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`lesson_progress_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`finished_at`	ISO 8601 formatted datetime string indicating when the user finished the lesson content. Setting this field will also mark the lesson complete unless the lesson requires validation, such as a review of proctoring.	`String`
`completed_at`	ISO 8601 formatted datetime string indicating when the user completed the lesson. If null, the user has not completed the lesson.	`String`
`success_status`	'PASSED', 'FAILED' or null	`Enum`
`score`	Score received	`Integer`
`max_score`	Max possible score	`Integer`
`custom_data`		`String`
`validation_status`	'PASSED', 'FAILED' or null	`Enum`
`validation_data`	JSON formatted. Ignored if the lesson does not require validation.	`Object`

offers

list

GET /v1/offers

List Offers. Returns a paginated list (1000 results per page) based upon the filters supplied.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

read

GET /v1/offers/{offer_id}

Get Offer details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`offer_id` required		`String`

paths

list

GET /v1/paths

List Paths. Returns a paginated list (100 results per page) based upon the filters supplied. Example Response: { "count": 1, "next": null, "previous": null, "results": [ "path": { "id": "cdefghi345678", "title": "Example Path Title", "path_item_count": 0 } ] }

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

read

GET /v1/paths/{id}

Get Path details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`id` required		`String`

path-items > list

GET /v1/paths/{path_id}/path-items

Returns a list of Path Item objects Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "qwerty1234", "slug": "test-path-1", "course": { "id": "abcdefg1234", "title": "Test Path Course 1", "lesson_count": 3, "required_lesson_count": 3 } } ] }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`path_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

path-items > read

GET /v1/paths/{path_id}/path-items/{id}

Returns a single Path Item object and its details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`path_id` required		`String`
`id` required		`String`

ping

list

GET /v1/ping

Ping the API endpoint. HTTP 2xx responses indicate a successful authentication with the Skilljar API endpoint.

progresstokens

update

PUT /v1/progresstokens/{progress_token_id}

Update the progress based on the given progress token. May update the corresponding lesson progress for the user, and update course status if this action completes the course.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`progress_token_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`completed_at`	ISO 8601 formatted datetime string indicating when the user completed the task	`String`
`success_status`		`Enum`
`score`	Score received	`Integer`
`max_score`	Max possible score	`Integer`

partial_update

PATCH /v1/progresstokens/{progress_token_id}

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`progress_token_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`completed_at`	ISO 8601 formatted datetime string indicating when the user completed the task	`String`
`success_status`		`Enum`
`score`	Score received	`Integer`
`max_score`	Max possible score	`Integer`

GET /v1/promo-code-pools

List PromoCodePools. Returns a paginated list (1000 results per page) based upon the filters supplied.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`offer_id`	Filter results by the id of a Offer	`String`
`name`	Filter results by PromoCodePool name	`String`

POST /v1/promo-code-pools

Create a PromoCodePool Example POST body (if POSTing JSON rather than form-encoded parameters): { "name": "promo-code-pool-name-1", "active": true, "discount_type": "PERCENT_OFF", "percent_off": 100, "single_use_per_user": false, "starts_at": "2018-03-16T16:45:55.946094Z", "expires_at": "2018-10-16T16:45:55.946094Z", } Or { "name": "promo-code-pool-name-1", "active": true, "discount_type": "PRICE_OVERRIDE", "price_cents": 5000, "single_use_per_user": false, "starts_at": "2018-03-16T16:45:55.946094Z", "expires_at": "2018-10-16T16:45:55.946094Z", }

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name` required		`String`
`active`		`Boolean`
`starts_at` required	ISO 8601 formatted datetime string indicating the start of the promo code pool	`String`
`expires_at`	ISO 8601 formatted datetime string indicating the expiration of the promo code pool	`String`
`expire_content`		`Boolean`
`discount_type` required		`Enum`
`price_cents`		`Integer`
`percent_off`		`Integer`
`single_use_per_user`		`Boolean`

GET /v1/promo-code-pools/{promo_code_pool_id}

Get PromoCodePool details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`

PUT /v1/promo-code-pools/{promo_code_pool_id}

Update for promo-code-pools.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name` required		`String`
`active`		`Boolean`
`starts_at` required		`String`
`expires_at`	ISO 8601 formatted datetime string indicating the expiration of the promo code pool	`String`
`expire_content`		`Boolean`

PATCH /v1/promo-code-pools/{promo_code_pool_id}

Update for promo-code-pools. PUT and PATCH are identical - both do partial updates

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`name`		`String`
`active`		`Boolean`
`starts_at`		`String`
`expires_at`	ISO 8601 formatted datetime string indicating the expiration of the promo code pool	`String`
`expire_content`		`Boolean`

DELETE /v1/promo-code-pools/{promo_code_pool_id}

Deletes a PromoCodePool record. As a result, the associated PromoCode will also be deleted. Any purchases that used the previously associated PromoCode will now be updated to have a null value for code_used. This action cannot be undone.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`

GET /v1/promo-code-pools/{promo_code_pool_id}/offers

List PromoCodePoolOffers. Returns a paginated list (1000 results per page) based upon the filters supplied.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`

POST /v1/promo-code-pools/{promo_code_pool_id}/offers

Attach an Offer to a PromoCodePool. There is a limit of 500 offers that can be added to a PromoCodePool per transaction. Example POST body (if POSTing JSON rather than form-encoded parameters): { "id": "abcde12345" } Or [ {"id": "bcdef23456"}, {"id": "cdefg34567"}, {"id": "defgh45678"}, {"id": "efghi56789"} ]

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`id`	Offer ID you wish to attach to a PromoCodePool	`String`

DELETE /v1/promo-code-pools/{promo_code_pool_id}/offers/{offer_id}

Removes an Offer from a PromoCodePool. Does not delete the Offer or PromoCodePool

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_pool_id` required		`String`
`offer_id` required		`String`

GET /v1/promo-codes

List PromoCodes. Returns a paginated list (1000 results per page) based upon the filters supplied.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`promo_code_pool_id`	Filter results by the id of a Offer	`String`
`code`	Filter results by the code used - case sensitive	`String`
`active`	Filter results by active (true or false)	`String`

POST /v1/promo-codes

Create a PromoCode. A PromoCodePool must exist before attempting to post to this endpoint. Example POST body (if POSTing JSON rather than form-encoded parameters): { "code": "6hhzj2ea-v5j3ak3d", "max_uses": 30, "active": true, "promo_code_pool_id": "9uips0sdja", }

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`code` required		`String`
`max_uses` required		`Integer`
`active`		`Boolean`
`promo_code_pool_id` required		`String`

GET /v1/promo-codes/{promo_code_id}

Get PromoCode details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_id` required		`String`

PUT /v1/promo-codes/{promo_code_id}

Update for promo-codes. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`code` required		`String`
`max_uses` required		`Integer`
`active`		`Boolean`

PATCH /v1/promo-codes/{promo_code_id}

Update for promo-codes. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`code`		`String`
`max_uses`		`Integer`
`active`		`Boolean`

DELETE /v1/promo-codes/{promo_code_id}

Deletes a PromoCode record. This action cannot be undone.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`promo_code_id` required		`String`

purchases

read

GET /v1/purchases/{purchase_id}

Get purchase details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`purchase_id` required	ID of a Purchase object	`String`

Response Object

The response object is "application/JSON" encoded object, containing the following items.

Parameter	Description
`id`	(Internal) ID of the Purchase object
`user`	User object that made the Purchase object
`status_msg`	Status message if the payment for the Purchase failed
`purchased_at`	Date the Purchase object was created
`refunded_at`	Date (if) the Purchase objected was refunded
`refund_cents`	Amount (if) the Purchase objected was refunded
`payment_processor`	Payment processor used
`order_id`	A unique order ID for the Purchase
`price_cents`	Price (in cents) of the Purchase made
`quantity`	Amount of items purchased
`offer_id`	(Internal) ID of the Offer purchased
`offer_sku`	(Internal) SKU of the Offer purchased
`offer_description`	Description of the Offer purchased
`offer_price_cents`	Price (in cents) of the Offer purchased
`promo_code_price_cents`	Price (in cents) of the PromoCode used
`promo_code_percent_off`	Percentage the PromoCode discounted
`promo_code_quantity`	Amount of PromoCodes used
`tax_price_cents`	Price (in cents) of local tax on the Purchase
`payment_processor_order_id`	ID for the payment processor used
`payment_processor_response_data`	Response from the payment processor used
`currency_code`	Type of currency used for the Purchase

update

PUT /v1/purchases/{purchase_id}

Update purchase details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`purchase_id` required		`String`

Request Body

The request body should be "application/JSON" encoded, and should contain a single item.

Parameter	Description	Type
`state`	'PENDING', 'SUCCESS', 'FAILED', 'REFUNDED', or 'CANCELLED'	`Enum`
`refunded_at`		`String`
`refund_cents`		`Integer`
`price_cents`		`Integer`
`tax_price_cents`		`Integer`

partial_update

PATCH /v1/purchases/{purchase_id}

Update purchase details. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`purchase_id` required		`String`

Request Body

The request body should be "application/JSON" encoded, and should contain a single item.

Parameter	Description	Type
`state`	'PENDING', 'SUCCESS', 'FAILED', 'REFUNDED', or 'CANCELLED'	`Enum`
`refunded_at`		`String`
`refund_cents`		`Integer`
`price_cents`		`Integer`
`tax_price_cents`		`Integer`

fulfill

POST /v1/purchases/{purchase_id}/fulfill

Fulfill specific purchase. Updates the purchase state, and if "SUCCESS", fulfills the purchase, creating any necessary course or domain registrations.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`purchase_id` required		`String`

Request Body

The request body should be "application/JSON" encoded, and should contain a single item.

Parameter	Description	Type
`state` required	'SUCCESS', 'FAILED', or 'CANCELLED'	`Enum`
`error_msg`	Optional: This error message will be presented to the user after they return to Skilljar, and will be set as the status_msg on the Purchase	`String`
`payment_processor_order_id`	Optional: The id of the transaction within the payment processor system, for reference only	`String`
`payment_processor_response_data`	Optional: Purchase metadata. For reference only. JSON format is recommended	`String`

training-credit-codes

list

GET /v1/training-credit-codes

List Training-Credit Codes. Returns a paginated list (1000 results per page) based upon the filters supplied.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`tracking_identifier`	Filter results by tracking_identifier	`String`
`training_credit_code`	Filter results by training credit code name	`String`

create

POST /v1/training-credit-codes

Create a training credit code.

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`training_credit_code` required	String used by Learners to apply Training Credit balance on the course platform and purchase Training content.	`String`
`credits_total` required	Total number of credits stored on this code.	`Integer`
`expiration_date`	ISO 8601 formatted datetime string indicating the expiration of the training credit code	`String`
`expire_content`	If true, when this code is used, learners will lose access to content when the code expires.	`Boolean`
`tracking_identifier`	Custom string for teams to identify codes in Financial/reporting tools. Is not used by Skilljar.	`String`
`available_to_all_students`	Set to "true" if all learners should be able to use this credit code.	`Boolean`
`student_groups`	Required if the above option is "false". Use this format to include student_group ids: ["2d4EXAMPLE0ea32j", "2d4EXAMPLE20esh5y"]	`Array`
`available_for_all_offers`	Set to "true" if this credit code should be available for all existing and future offers that have credit value.	`Boolean`
`offers`	Required if the above option is "false". Use this format to include offer_ids: ["2d4EXAMPLE0ea32j", "2d4EXAMPLE20esh5y"]	`Array`

read

GET /v1/training-credit-codes/{training_credit_code_id}

Get single tcc details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`training_credit_code_id` required		`String`

partial_update

PATCH /v1/training-credit-codes/{training_credit_code_id}

Update a training credit code.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`training_credit_code_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`credits_total`		`Integer`
`expiration_date`	ISO 8601 formatted datetime string indicating the expiration of the training credit code	`String`
`expire_content`	If true, when this code is used, learners will lose access to content when the code expires.	`Boolean`
`tracking_identifier`	Custom string for teams to identify codes in Financial/reporting tools. Is not used by Skilljar.	`String`
`available_to_all_students`	Set to "true" if all learners should be able to use this credit code.	`Boolean`
`student_groups`	Required if the above option is "false". Use this format to add or remove student_group ids - Add resolves first, then Remove: { "add": ["2d4EXAMPLE0ea32j", "2d4EXAMPLE20esh5y"], "remove": ["9k4EXAMPLE20h5ysK"] }	`Object`
`available_for_all_offers`	Set to "true" if this credit code should be available for all existing and future offers that have credit value.	`Boolean`
`offers`	Required if the above option is "false". Use this format to add or remove offer_ids - Add resolves first, then Remove: { "add": ["2d4EXAMPLE0ea32j", "2d4EXAMPLE20esh5y"], "remove": ["9k4EXAMPLE20h5ysK"] }	`Object`

users

list

GET /v1/users

List users who have registered on at least one domain. Returns a paginated list (1000 results per page) of users.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`email`	Filter users by email address	`String`
`first_name`	Filter users by first name - case sensitive	`String`
`last_name`	Filter users by last name - case sensitive	`String`

read

GET /v1/users/{user_id}

Get user's course registration overview.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`

update

PUT /v1/users/{user_id}

Update for user details. Only name and email address may be changed. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`email`	Email address	`String`
`first_name`	First name	`String`
`last_name`	Last name	`String`

partial_update

PATCH /v1/users/{user_id}

Partial update for user details. Only name and email address may be changed. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`email`	Email address	`String`
`first_name`	First name	`String`
`last_name`	Last name	`String`

anonymize

POST /v1/users/{user_id}/anonymize

Obfuscate all data that could be used to identify the user, either directly, or indirectly. This will permanently update the user, deleting sensitive information and preventing future usage of the platform. This action is not reversible.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`

groups > list

GET /v1/users/{user_id}/groups

List groups of which a user is a member.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

published-courses > list

GET /v1/users/{user_id}/published-courses

List published courses with progress details for a user. Returns a paginated list (1000 results per page) of course progress details for a user.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

published-courses > read

GET /v1/users/{user_id}/published-courses/{published_course_id}

Get course progress details for a user.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`

published-courses > update

PUT /v1/users/{user_id}/published-courses/{published_course_id}

Update course progress for a user. PUT and PATCH are identical - both do partial updates. To mark a course as complete, you only need to set the completed_at within the course progress. For example: { "course_progress": { "completed_at": "2015-06-03T01:02:03.012345Z", "success_status": "PASSED" } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`published_course_id`	ID of the PublishedCourse	`String`
`course_progress` required		`Object`

published-courses > partial_update

PATCH /v1/users/{user_id}/published-courses/{published_course_id}

Partial update course progress for a user. PUT and PATCH are identical - both do partial updates. To mark a course as complete, you only need to set the completed_at within the course progress. For example: { "course_progress": { "completed_at": "2015-06-03T01:02:03.012345Z", "success_status": "PASSED" } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`published_course_id`	ID of the PublishedCourse	`String`
`course_progress`		`Object`

published-courses > lessons > list

GET /v1/users/{user_id}/published-courses/{published_course_id}/lessons

List lessons with progress details for a user in a particular course. Returns a paginated list (100 results per page) of lesson progress details for a user.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

published-courses > lessons > read

GET /v1/users/{user_id}/published-courses/{published_course_id}/lessons/{lesson_id}

Get lesson progress details for a user.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`
`lesson_id` required		`String`

published-courses > lessons > update

PUT /v1/users/{user_id}/published-courses/{published_course_id}/lessons/{lesson_id}

Update lesson progress for a user. PUT and PATCH are identical - both do partial updates. To mark a lesson as complete, you only need to set the completed_at within the lesson progress. For example: { "lesson_progress": { "completed_at": "2015-06-03T01:02:03.012345Z" } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`
`lesson_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`lesson_progress` required		`Object`

published-courses > lessons > partial_update

PATCH /v1/users/{user_id}/published-courses/{published_course_id}/lessons/{lesson_id}

Partial update lesson progress for a user. PUT and PATCH are identical - both do partial updates. To mark a lesson as complete, you only need to set the completed_at within the lesson progress. For example: { "lesson_progress": { "completed_at": "2015-06-03T01:02:03.012345Z" } }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`user_id` required		`String`
`published_course_id` required		`String`
`lesson_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`lesson_progress`		`Object`

vilt-session-events

list

GET /v1/vilt-session-events

List ViltSessionEvents. Returns a paginated list based upon the filters supplied.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`session__lesson__course__id`	Filter ViltSessionEvents by exact match of a Course ID	`String`
`session__lesson__id`	Filter ViltSessionEvents by exact match of a Lesson ID	`String`
`starts_at__gte`	Filter where a ViltSessionEvent is greater than or equal to the starts at value. Datetime format	`String`
`ends_at__lte`	Filter where a ViltSessionEvent is less than or equal to the ends at value. Datetime format	`String`

read

GET /v1/vilt-session-events/{vilt_session_event_id}

Get ViltSessionEvent details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`vilt_session_event_id` required		`String`

vilt-session-registrations

list

GET /v1/vilt-session-registrations

List ViltSessionRegistrations. Returns a paginated list (1000 results per page) based upon the filters supplied.

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`
`page_size`	Number of results to return per page.	`Integer`
`session__id`	Filter results by the id of a ViltSession	`String`

create

POST /v1/vilt-session-registrations

Register a user to a vilt_session. An enrollment for this user must exist before attempting to post to this endpoint. Example POST body (if POSTing JSON rather than form-encoded parameters): { "vilt_session": { "id": "jaso89ajs", }, "enrollment_id": "9uips0sdja" }

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`vilt_session`		`Object`
`enrollment_id`		`String`

read

GET /v1/vilt-session-registrations/{vilt_session_registration_id}

Get ViltSessionRegistration details

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`vilt_session_registration_id` required		`String`

update

PUT /v1/vilt-session-registrations/{vilt_session_registration_id}

Update for vilt-session-registrations. Only attendance may be changed. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`vilt_session_registration_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`attended` required		`Boolean`

partial_update

PATCH /v1/vilt-session-registrations/{vilt_session_registration_id}

Update for vilt-session-registrations. Only attendance may be changed. PUT and PATCH are identical - both do partial updates.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`vilt_session_registration_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`attended`		`Boolean`

delete

DELETE /v1/vilt-session-registrations/{vilt_session_registration_id}

Deletes a ViltSessionRegistration record, marks student as unattended for the ViltSessionEvent. This action cannot be undone.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`vilt_session_registration_id` required		`String`

webhooks

list

GET /v1/webhooks

List webhooks. Returns a paginated response (100 results per page) of webhooks. Example Response: { "count": 1, "next": null, "previous": null, "results": [ { "id": "abcd1234", "target_url": "http://example.com/skilljar-hook-processor", "event_type": null, "active": true, "deactivate_reason": null } ] }

Query Parameters

The following parameters should be included as part of a URL query string.

Parameter	Description	Type
`page`	A page number within the paginated result set.	`Integer`

create

POST /v1/webhooks

Create a webhook. The Skilljar system will send HTTP POST requests to the given URL when events occur within the platform. If the "event_type" field is null, all events will be sent to the given URL. If the field is set, only events matching the type provided will be sent to the given URL. If multiple webhooks qualify for an event and have the same URL, the event will be sent to the URL only once.

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`target_url` required		`String`
`active`		`Boolean`
`event_type`	'COURSE_COMPLETION', 'COURSE_ENROLLMENT', 'DOMAIN_ENROLLMENT', 'LESSON_COMPLETION', 'PATH_COMPLETION', 'PATH_ENROLLMENT', 'PURCHASE_FULFILLMENT', 'QUIZ_COMPLETION', or null. If null, all events, regardless of type, will be sent to the webhook URL.	`Enum`

read

GET /v1/webhooks/{webhook_id}

Get webhook details. Example Response: { "id": "abcd1234", "target_url": "http://example.com/skilljar-hook-processor", "event_type": null, "active": true, "deactivate_reason": null }

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`webhook_id` required		`String`

update

PUT /v1/webhooks/{webhook_id}

Update webhook details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`webhook_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`target_url` required		`String`
`active`		`Boolean`
`event_type`	'COURSE_COMPLETION', 'COURSE_ENROLLMENT', 'DOMAIN_ENROLLMENT', 'LESSON_COMPLETION', 'PATH_COMPLETION', 'PATH_ENROLLMENT', 'PURCHASE_FULFILLMENT', 'QUIZ_COMPLETION', or null. If null, all events, regardless of type, will be sent to the webhook URL.	`Enum`

partial_update

PATCH /v1/webhooks/{webhook_id}

Update webhook details.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`webhook_id` required		`String`

Request Body

The request body should be "application/json" encoded, and should contain a single item.

Parameter	Description	Type
`target_url`		`String`
`active`		`Boolean`
`event_type`	'COURSE_COMPLETION', 'COURSE_ENROLLMENT', 'DOMAIN_ENROLLMENT', 'LESSON_COMPLETION', 'PATH_COMPLETION', 'PATH_ENROLLMENT', 'PURCHASE_FULFILLMENT', 'QUIZ_COMPLETION', or null. If null, all events, regardless of type, will be sent to the webhook URL.	`Enum`

delete

DELETE /v1/webhooks/{webhook_id}

Delete webhook.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`webhook_id` required		`String`

ping > create

POST /v1/webhooks/{webhook_id}/ping

Sends an HTTP POST event of type=PING to the webhook. Failure will not deactivate the webhook, and it does not retry.

Path Parameters

The following parameters should be included in the URL path.

Parameter	Description	Type
`webhook_id` required		`String`

sample-course-completion > list

GET /v1/webhooks/sample-course-completion

Returns a single-item list of sample course completion events. The sample event returned by this API is either the most recent COURSE_COMPLETION event, or a sample event with sample data if there are no course completions. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-course-enrollment > list

GET /v1/webhooks/sample-course-enrollment

Returns a single-item list of sample course enrollment events. The sample event returned by this API is either the most recent COURSE_ENROLLMENT event, or a sample event with sample data if there are no course enrollments. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-domain-enrollment > list

GET /v1/webhooks/sample-domain-enrollment

Returns a single-item list of sample domain enrollment events. The sample event returned by this API is either the most recent DOMAIN_ENROLLMENT event (if the most recent domain membership has signup info that corresponds with current active signup fields), or a sample event with sample data if there are no domain memberships. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-lesson-completion > list

GET /v1/webhooks/sample-lesson-completion

Returns a single-item list of sample lesson completion events. The sample event returned by this API is either the most recent LESSON_COMPLETION event, or a sample event with sample data if there are no lesson completions. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-path-completion > list

GET /v1/webhooks/sample-path-completion

Returns a single-item list of sample path completion events. The sample event returned by this API is either the most recent PATH_COMPLETION event, or a sample event with sample data if there are no path completions. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-path-enrollment > list

GET /v1/webhooks/sample-path-enrollment

Returns a single-item list of sample path enrollment events. The sample event returned by this API is either the most recent PATH_ENROLLMENT event, or a sample event with sample data if there are no path enrollments. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-purchase-fulfillment > list

GET /v1/webhooks/sample-purchase-fulfillment

Returns a single-item list of sample purchase fulfillment events. The sample event returned by this API is either the most recent PURCHASE_FULFILLMENT event, or a sample event with sample data if there are no purchase fulfillment events. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.

sample-quiz-completion > list

GET /v1/webhooks/sample-quiz-completion

Returns a single-item list of sample quiz completion events. The sample event returned by this API is either the most recent QUIZ_COMPLETION event, or a sample event with sample data if there are no quiz completions. This API is used internally to generate sample data; the body of an actual webhook notification will be a single JSON event that is NOT contained within a list.