Freshservice

Connect Freshservice to collect ticketing evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Freshservice:

   1. Log in to your Freshservice support portal.
   2. Click your profile picture in the top right corner and go to the Profile settings page.
   3. Copy your API key, shown below the change password section on the right.

   Where to find the other values:

   • Domain: The part before .freshservice.com in your Freshservice address (https://yourdomain.freshservice.com).

   The API key acts with the agent's own permissions; there is no read-only key, so use an agent whose role only views tickets. Freshservice also supports OAuth 2.0 with per-endpoint scopes (the fetched page names freshservice.tickets.create as an example); the click path to create an OAuth app was not on the fetched page. Username/password basic auth was deprecated on May 31, 2023. Verification: the fetched page does not say whether the key can be viewed again.

   Source: api.freshservice.com, checked 2026-10-07.

   The permissions Safeguard needs: freshservice.tickets.view.

2. On Compliance › Connectors, open Freshservice, click Connect, choose API token and fill in:

   Field	What to enter
   Domain	Optional. The part before .freshservice.com in your address.
   API key	Optional. Stored encrypted and never shown again.

   Or, instead: Access token (optional).

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Freshservice and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Ticketing 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