There are different options for integrations:
These can be utilised to create deep links to the content items, enabling the user to discover and launch content directly from Fuse. You can also choose to import your content from third-party libraries into Fuse to take advantage of our deeper functionality.
This document will detail how you can build your own integration or use Fuse services to build in partnership.
KI connectors are pre built connectors that surface content from third-party libraries into Fuse via our intelligent search engine. At present, we support the following libraries:
To set up your LinkedIn Learning connector, please raise a ticket with Fuse support including the following information:
Parameter
|
Description
|
Sample Value
|
Client ID
|
LinkedIn Learning client ID
|
78kasaf1g2042fs02a
|
Client secret
|
LinkedIn Learning secret key
|
HgfGEx2GS2eGjeH8Q
|
community_id
|
Community ID that controls visibility of content.
|
12424
|
We recommend that you generate a new application in the LinkedIn Learning admin panel (called Generate LinkedIn Learning REST API Application under Integrations) and call it Fuse. This will allow you to manage the keys for Fuse separately to other integrations. You can access the LinkedIn Learning documentation here.
Note: The Community ID is used to control visibility of LinkedIn Learning results in search. Only users who are a member of the specified community will have visibility. We recommend you create a community for LinkedIn Learning and provide this ID. Doing so will enable you to control membership against your purchased licences. If you have purchased an enterprise licence, you can provide the global community ID, which will make it available for all.
Fuse can integrate with third-party libraries using our range of open APIs for content management. There are two options available:
To create deep links, you can use the ‘External Link’ content type within Fuse. This creates a content item within Fuse that, when clicked, will push the user back to the course on the third-party platform to complete the training.
To do this, you use the POST /contents/link endpoint.
https://<instance_name>.fuseuniversal.com/api/<version>/contents/link
Parameter
|
Data Type
|
Description
|
Required?
|
Sample Value
|
name
|
string
|
Title of content
|
Yes
|
Basics of Health & Safety
|
description
|
string
|
Description of content
|
Yes
|
Ensure you and your team are comprehensively trained to carry out your work safely.
|
original_url
|
string
|
URL of content in content library
|
Yes
|
https://www.acme-content-library.com/COURSE001/course001
|
thumbnail
|
file
|
Image file to use
|
No. Default used if no thumbnail provided
|
Filename.jpg
|
tag_list
|
string
|
List of content tags
|
No
|
compliance, health and safety, onboarding
|
community_ids
|
array[int]
|
Array of community IDs to add content to
|
Yes
|
1210, 1402, 1842
|
share_attributes[note]
|
string
|
Notification message
|
No, not recommended.
|
This is to confirm upload.
|
share_attributes[community_ids]
|
array[int]
|
Array of community IDs to notify
|
No, not recommended. This will notify ALL users of these communities.
|
[1210, 1402, 1842]
|
share_attributes[user_ids]
|
array[int]
|
Array of user IDs to notify
|
No, not recommended.
|
[23232, 92014]
|
To bring content in there are two options:
You can also choose to create content natively within Fuse. This will take the content file and import it into Fuse. There are several benefits of choosing this method:
To do this, you use the POST /contents/media endpoint.
https://<instance_name>.fuseuniversal.com/api/<version>/contents/media
Note: you must use v4.3 or later, Fuse supports SCORM 1.2.
Parameter
|
Data Type
|
Description
|
Required?
|
Sample Value
|
name
|
string
|
Title of content
|
Yes
|
Basics of Health & Safety
|
description
|
string
|
Description of content
|
Yes
|
Ensure you and your team are comprehensively trained to carry out your work safely.
|
composite_attributes[type]
|
string
|
File type:
|
Yes
|
Video
|
composite_attributes[file]
|
file
|
The file for the content
|
Yes
|
filename.ext
|
thumbnail
|
file
|
Image file to use
|
No. Default used if no thumbnail provided
|
thumbnail.jpg
|
tag_list
|
string
|
List of content tags
|
No
|
compliance, health and safety, onboarding
|
community_ids
|
array[int]
|
Array of community IDs to add content to
|
Yes
|
1210, 1402, 1842
|
share_attributes[note]
|
string
|
Notification message
|
No, not recommended.
|
This is to confirm upload.
|
share_attributes[community_ids]
|
array[int]
|
Array of community IDs to notify
|
No, not recommended.
|
[1210, 1402, 1842]
|
share_attributes[user_ids]
|
array[int]
|
Array of user IDs to notify
|
No, not recommended.
|
[23232, 92014]
|
If you create content natively in Fuse but you require completion data to be synced back to the third-party platform (or directly to your HRIS platform) you can use Fuse’s webhooks for SCORM course completions.
To set up, you will need to provide the webhook URL. You can do this during your implementation process, or via Fuse Support when in-life.
When a SCORM course is completed, Fuse will send a POST request to the URL with following parameters:
Parameter
|
Description
|
Sample Value
|
user_id=<id>
|
Fuse ID of the user
|
12414
|
content_id=<id>
|
Content ID completed
|
42140
|
Please note: Additional logic is required client-side to match the Fuse content ID with the third-party library or HRIS system. This is usually done by making an additional call to the Fuse API to get the details using the Fuse Content ID. This is also where additional metadata, such as quiz score, can be obtained.
If you don’t have the capabilities in-house, we also provide integration services to build this for you. If the third-party content library allows, a CSV containing links to their content can be uploaded to a secure FTP folder. We will then configure our middleware to import the CSV and update your Fuse instance with the deep links.
Due to the customisable nature of Fuse this is a custom process for each customer. The automated CSV process is typically scoped and developed as part of the initial Fuse implementation process.
The scope of the process will be defined in a Statement of Work beforehand. Once approved, it will typically take 8 to 10 working days to develop, test and deploy. Timescales are dependent on the customer providing the necessary test data and data validation.
Note: This is a chargeable service, please refer to your Account Manager for more information.
The process will be developed and tested on the customer’s Staging instance first, before being deployed to their Production instance once approved.
Once live, change requests and issues should be raised via the Fuse support ticketing system.
If the content provider allows it, content can be remotely hosted on Fuse. There are several benefits of choosing this method:
© 2022 Fuse Universal - All Rights Reserved