Skip to main content

Thrive Learning

Thrive Learning is a learning platform (LMS/LXP) that helps organizations deliver training, manage learners, and track content completions. The Thrive API is a REST API served from https://public.api.learn.link that exposes users, content, activities, completions, assignments, and audiences. Nexla connects to this API to ingest learning data into your pipelines and to push users, completions, and assignments back into Thrive.

Thrive Learning icon

Power end-to-end data operations for your Thrive Learning API with Nexla. Our bi-directional Thrive Learning connector is purpose-built for Thrive Learning, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Thrive Learning or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Thrive Learning workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Thrive Learning API uses HTTP Basic authentication. The username is your Thrive tenant ID (a unique customer identifier), and the password is an API key generated for that tenant.

To obtain your credentials:

  1. Contact the Thrive Support team to obtain the tenant ID for your environment. Tenant IDs differ between the live and staging environments, so confirm you are using the correct one.

  2. Have a site administrator generate an API key for your tenant through the Thrive administration tools. Treat the API key as a secret; never share it or commit it to a source repository.

  3. Confirm that your credentials work against the live API base URL, https://public.api.learn.link/rest/v1. All requests must be made over HTTPS.

For details on authentication and available endpoints, see the Thrive API documentation.

Authenticate

Credentials required

FieldRequiredSecretDescription
UsernameYesNoUsername for authenticating to the Thrive Learning API.
PasswordYesYesPassword for authenticating to the Thrive Learning API.

Create a credential in Nexla

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your Thrive tenant ID in the Username field.

  4. Enter your Thrive API key in the Password field.

    The Thrive API key is sensitive. If it is ever exposed, have a site administrator revoke it and generate a new one, then update this credential in Nexla.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Thrive Learning connector tile, then select the credential that will be used to connect to the Thrive Learning instance, and click Next; or, create a new Thrive Learning credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Thrive Learning endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Users

Retrieve users from Thrive Learning.

  • This endpoint returns a paginated list of users. Nexla automatically follows pagination to fetch all available records.

[Rest API] List Content

Retrieve content items from Thrive Learning.

  • This endpoint returns a paginated list of content. Nexla automatically follows pagination to fetch all available records.

[Rest API] List Activities

Retrieve activities from Thrive Learning.

  • This endpoint returns a paginated list of activities. Nexla automatically follows pagination to fetch all available records.

[Rest API] List Completions

Retrieve a list of content completion records for users.

  • Optional filters let you narrow results by content ID, user ID, RPL-import status, and a completed-date range (start and end).

For details on the response fields and filter parameters, see the Thrive completions documentation.

[Rest API] List Assignments

Retrieve a list of assignments enrolling users in content.

  • Optional filters let you narrow results by audience ID or reference, and by an "updated since" ISO 8601 date-time to return only assignments modified on or after that time.

For details on the response fields and filter parameters, see the Thrive assignments documentation.

[Rest API] List Audiences

Retrieve learner groups (audiences) used to target content and assignments.

  • Optional filters let you narrow results by API-controlled status and by an "updated since" ISO 8601 date-time to return only audiences modified on or after that time.

For details on the response fields and filter parameters, see the Thrive audiences documentation.

[Rest API] List CPD User Summaries

Retrieve per-user continuing professional development (progress) summaries for a date range.

  • An entry-date range is required: provide both an "entry date from" and an "entry date to" value in YYYY-MM-DDThh:mm:ss format. You can optionally restrict results to a comma-separated list of user IDs.

For details on the response fields and filter parameters, see the Thrive CPD summaries documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Thrive Learning data sources can also be manually configured to ingest data from any valid Thrive Learning API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Thrive Learning data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Thrive Learning destination, and select the Send to Destination option from the menu. Select the Thrive Learning connector from the list of available destination connectors, then select the credential that will be used to connect to Thrive Learning, and click Next; or, create a new Thrive Learning credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Thrive Learning endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create User

Create a new user in Thrive Learning.

  • Each record from your Nexset is sent as a JSON request body to create a new user. Ensure records include the fields Thrive requires for user creation.

For the required request body fields, see the Thrive create-user documentation.

[Rest API] Update User

Update an existing user by their reference identifier.

  • Each record from your Nexset is sent as a JSON request body to update the user identified by their reference. Include the user reference and the fields you want to change.

For the request body and reference format, see the Thrive update-user documentation.

[Rest API] Create Completion

Create a content completion record for a user.

  • Each record from your Nexset is sent as a JSON request body to record a completion. Ensure records include the content and user references Thrive requires.

For the required request body fields, see the Thrive create-completion documentation.

[Rest API] Create Assignment

Create a new assignment to enroll users in content.

  • Each record from your Nexset is sent as a JSON request body to create an assignment. Ensure records include the audience and content references Thrive requires.

For the required request body fields, see the Thrive create-assignment documentation.

Manual configuration

Thrive Learning destinations can also be manually configured to send data to any valid Thrive Learning API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Thrive Learning endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Thrive Learning endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.