Skip to content
English
  • There are no suggestions because the search field is empty.

Thought Industries Integration

Overview

This integration enables seamless connectivity between Thought Industries (TI) and your external system for delivering and managing assessments. It leverages JWT-based Single Sign-On (SSO) and External Activities to securely pass learner and course data. 

Technical Requirements 

JWT Token Authentication
  • Signed using HS256 algorithm. 

  • Shared secret or API token required. 

Secure External URL 

  • Host an endpoint or landing page to receive and decode JWT tokens. 

Thought Industries API

Integration Flow 

1. Launch from Thought Industries 

  • Learner clicks an External Activity in TI. 

  • TI appends a JWT token to the configured URL as a query parameter (?jwt=...).

  • TI appends Certiverse Exam Code / SKU to the configured URL as a query parameter (?exam_id=...) 

2. JWT Token Details

  • Contains: 

    • Candidate Info: email, name 

    • Eligibility: course_id (use to look up additional data via API)

3. Eligibility end date

  • TI API used to look up purchase date
  • Eligibility end date set to purchase date + n days. 

4. Authentication 

  • Validate JWT using the shared secret. 

  • If user exists → log in. 

  • If user does not exist → create account and log in.

5. Booking Logic 

  • If pending booking exists for exam_id: 

    • Show dashboard with options: Start Exam, Cancel, or Reschedule. 

  • If no booking exists: 

    • Redirect to booking flow for the exam with eligibility end date applied.

6. Assessment Delivery 

  • Candidate completes the exam in your system. 

7. Result Posting 

  • Use Assignment External Activity API: 
    • Pass: 

      • status = completed 

      • grade feedback = "Great Job!" 

    • Fail: 

      • status = in-completed 

      • grade feedback = "Failed" 

      • Reset course progress and revoke access via TI API. 

External Activities Configuration

Token includes:

Security 

  • JWT signed with HS256. 

  • Validate signature using the shared secret before processing payload. 

  • Ensure HTTPS for all endpoints. 

Resources