Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Freshservice ITAM (BYOK) — connector documentation

  • MCP endpoint: https://byok-freshservice-itam.connectorbay.com/mcp
  • REST API: POST https://byok-freshservice-itam.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-freshservice-itam.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Freshservice ITAM Freshservice API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-freshservice-itam.connectorbay.com/health · Tool schemas: https://byok-freshservice-itam.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-freshservice-itam · agent@connectorbay.com

What Freshservice ITAM (BYOK) is for

Freshservice ITAM (BYOK) lets an AI assistant read your own Freshservice ITAM data through the Freshservice ITAM API with a key you supply (Freshservice API key). Read-only: 6 tools (list_itam_devices, list_itam_assets, list_physical_subtypes, list_lifecycle_events, list_cloud_infrastructures, list_cloud_resources). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.freshservice.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Freshservice ITAM. Freshservice ITAM and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "How many devices does Freshservice ITAM track and of which types?"
  • "Which assets are in Freshservice ITAM and who supplied them?"
  • "Which physical device subtypes exist in Freshservice ITAM?"
  • "What lifecycle events happened to Freshservice assets this year?"
  • "Which cloud accounts does Freshservice ITAM monitor?"
  • "Which cloud resources of type Mountpoint does Freshservice ITAM know?"

What it does

  • list_itam_devices: List discovered devices (physical, virtual, cloud) with name, type, impact, state, usage type, workspace, department and location id. Serial numbers, UUIDs and owner or user ids are not returned. Needs Freshservice IT Asset Management, which the vendor offers to accounts created after the 31 March 2026 release.
  • list_itam_assets: List ITAM assets (monitors, phones, peripherals) with name, type, service level, impact, usage type, vendor, building and department. Serial numbers, notes and owner or user ids are not returned. Needs Freshservice IT Asset Management, which the vendor offers to accounts created after the 31 March 2026 release.
  • list_physical_subtypes: List the device physical subtypes (blade, PDU, rack, storage room and so on) with id and name. Needs Freshservice IT Asset Management, which the vendor offers to accounts created after the 31 March 2026 release.
  • list_lifecycle_events: List asset lifecycle events (purchased, checked out, retired) with date, type, device and asset name. End-user names and notes are not returned. Needs Freshservice IT Asset Management, which the vendor offers to accounts created after the 31 March 2026 release.
  • list_cloud_infrastructures: List connected cloud accounts discovered by ITAM with name, tags, cloud vendor id, first-seen and last-changed times. Account identifiers and IP details are not returned. Needs Freshservice IT Asset Management, which the vendor offers to accounts created after the 31 March 2026 release.
  • list_cloud_resources: List discovered cloud resources (AWS and similar) with name, vendor resource type, region, zones, service level and first-seen time. Needs Freshservice IT Asset Management, which the vendor offers to accounts created after the 31 March 2026 release.

BYOK key

You bring your own Freshservice ITAM Freshservice API key (https://api.freshservice.com/#authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.freshservice.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Freshservice ITAM API (*.freshservice.com) with a BYOK key; documentation: https://api.freshservice.com/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Freshservice ITAM. Freshservice ITAM and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Freshservice ITAM account.

Built for: Worldwide. Languages: English.