Overview
Intercultural Teams supports LTI 1.3 (Learning Tools Interoperability), the industry standard for integrating learning tools with LMS platforms. This guide covers setup for any LTI 1.3 compliant platform not covered by our platform-specific guides.
Supported LTI services:
- LTI 1.3 Core (OIDC launch)
- Deep Linking 2.0 (content selection)
- Assignment and Grade Services 2.0 (grade passback)
- Names and Role Provisioning Services (roster sync)
Prerequisites
- An LMS or learning platform that supports LTI 1.3
- Admin access to your platform's LTI tool management
- Intercultural Teams enterprise account with admin access
Intercultural Teams LTI Endpoints
Use these URLs when registering Intercultural Teams as a tool in your platform:
| Endpoint | URL |
|---|---|
| Login Initiation URL | https://interculturalteams.com/lti/login |
| Launch URL (Target Link URI) | https://interculturalteams.com/lti/launch |
| JWKS URL (Public Key Set) | https://interculturalteams.com/lti/jwks |
| Deep Linking URL | https://interculturalteams.com/lti/deep-link |
| Redirect URI | https://interculturalteams.com/lti/launch |
Step 1: Register Intercultural Teams in Your Platform
- Open your platform's LTI tool management (often under Admin > Integrations or Settings > LTI)
- Add a new LTI 1.3 Tool or External Tool Provider
- Enter the Intercultural Teams endpoints from the table above
- Your platform will generate:
- Client ID — unique identifier for this registration
- Deployment ID — identifies this deployment within the platform
- Note your platform's:
- Issuer URL — the platform's identity (usually the base URL)
- Authorization URL — OAuth2 authorization endpoint
- Token URL — OAuth2 token endpoint
- JWKS URL — the platform's public key set
Step 2: Configure the Platform in Intercultural Teams
- Navigate to Admin > L&D Plugins
- Click Add Platform and fill in:
- Name: A descriptive name for this integration
- Platform Type: Generic LTI 1.3 Platform
- Issuer URL: Your platform's issuer
- Client ID: From Step 1
- Auth Login URL: Your platform's authorization endpoint
- Auth Token URL: Your platform's token endpoint
- JWKS URL: Your platform's JWKS endpoint
- Enable optional services:
- AGS (Grade Passback): If you want completion scores sent back to your platform
- NRPS (Roster Sync): If you want automatic user roster synchronisation
- Click Save — an RSA key pair is auto-generated
Step 3: Test the Launch
- In your platform, create a test assignment or course linked to Intercultural Teams
- Launch as a student — you should be redirected through the OIDC flow and land on the assigned content
- Verify the user account is automatically created in Intercultural Teams
Step 4: Content Deep Linking
- In your platform, use the "Select Content" or "Deep Link" option for Intercultural Teams
- The content picker will show available items:
- Pre-recorded Courses — Self-paced cultural training
- Cultural Scenarios — Interactive country-specific simulations
- Cultural Survey — Hofstede-based cultural profile assessment
- Tutor Booking — Book a live training session
- Country Briefs — Quick cultural reference guides
- Select content and confirm — it's now linked in your platform
Step 5: Grade Passback (Optional)
When AGS is enabled:
- Student completes an activity in Intercultural Teams
- A grade sync job is queued with the completion score
- The score is sent back to your platform via the AGS lineitem URL
- Monitor sync status in Admin > L&D Plugins > Grade Sync Log
LTI Claims Reference
Intercultural Teams reads these claims from the LTI 1.3 JWT:
| Claim | Required | Description |
|---|---|---|
iss |
Yes | Platform issuer URL |
aud |
Yes | Must match the Client ID |
sub |
Yes | Platform user ID |
nonce |
Yes | One-time-use value |
https://purl.imsglobal.org/spec/lti/claim/message_type |
Yes | Must be LtiResourceLinkRequest or LtiDeepLinkingRequest |
https://purl.imsglobal.org/spec/lti/claim/version |
Yes | Must be 1.3.0 |
https://purl.imsglobal.org/spec/lti/claim/deployment_id |
Yes | Deployment identifier |
https://purl.imsglobal.org/spec/lti/claim/target_link_uri |
Yes | Target content URL |
name |
No | User's full name |
email |
No | User's email (used for matching) |
Enterprise API (Optional)
For machine-to-machine integrations alongside LTI:
- Generate an API key in Admin > L&D Plugins > API Keys
- See the Enterprise API Reference for all endpoints
Troubleshooting
"Invalid message type" error
Intercultural Teams only accepts LtiResourceLinkRequest and LtiDeepLinkingRequest message types. Verify your platform is sending the correct type.
"Nonce already consumed" error Each launch must use a unique nonce. This error means the same nonce was sent twice — usually caused by the user refreshing the launch page. Have them re-launch from the platform.
JWKS verification fails Intercultural Teams caches platform JWKS for 24 hours. If your platform rotated keys, wait for the cache to refresh or contact support.
User created without email
If the platform doesn't send the email claim, Intercultural Teams creates a placeholder account. For best results, configure your platform to include user email in the LTI launch.
