TryHackMe
Connect TryHackMe to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your TryHackMe connection as security training evidence. Automated collection is not available for this provider yet.
| Category | Security Training |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In TryHackMe:
- Sign in to TryHackMe and open your organisation's management dashboard; company API keys are issued per organisation from there.
- Copy the company API key.
Where to find the other values:
- Base URL (optional): Leave blank for the current API, https://tryhackme.com/api/v2/external (the legacy https://tryhackme.com/external/api has two endpoints only).
- Account / Org / Workspace (optional): Not needed: a key identifies exactly one organisation and returns only that organisation's data.
TryHackMe's public documentation does not cover every step.
For TryHackMe business/education organisations. The key goes in the THM-API-KEY header. The article does not give the dashboard menu path or button labels for creating the key, and documents no read-only key type (the API includes seat write endpoints). Deactivating a key in the dashboard takes effect immediately.
Source: help.tryhackme.com, checked 2026-10-07.
-
On Compliance › Connectors, open TryHackMe, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads TryHackMe yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Security Training connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks