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

Freshservice (BYOK) — connector documentation

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

What Freshservice (BYOK) is for

Freshservice (BYOK) lets an AI assistant read your own Freshservice data through the Freshservice API with a key you supply (Freshservice API key). Read-only: 7 tools (list_tickets, get_ticket, list_requesters, list_agents, list_assets, list_changes, list_problems). 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. Freshservice 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:

  • "What are the latest Freshservice tickets?"
  • "Show Freshservice ticket 266"
  • "Find the Freshservice requester with email harry.potter@hogwarts.edu"
  • "Who are the active agents in Freshservice?"
  • "What assets are tracked in Freshservice?"
  • "What changes are planned in Freshservice?"

What it does

  • list_tickets: List Freshservice tickets (only those created in the last 30 days unless updated_since is given) with subject, status code, priority code, requester and dates.
  • get_ticket: Get one Freshservice ticket by id with its description text, status and priority codes, requester, category and approval state.
  • list_requesters: List Freshservice requesters (end users) with name, primary email, job title and active flag; can filter by email or phone and include agents.
  • list_agents: List Freshservice agents with name, email, job title, active flag and last login; can filter by active state or full-time versus occasional.
  • list_assets: List Freshservice assets (laptops, servers, monitors and so on) with name, tag, type id, usage and assignment. Valid for accounts created before 31 March 2026.
  • list_changes: List Freshservice change requests with subject, status, priority, risk, change type and planned start and end dates.
  • list_problems: List Freshservice problem records with subject, status, priority, impact, known-error flag and due date.

BYOK key

You bring your own Freshservice 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 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. Freshservice 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 account.

Built for: Worldwide. Languages: English.