Build on IntelliDesk: REST API, webhooks and MCP

Base URL https://intellidesk.co/api/v1. JSON in and out, 63 operations across 12 resources. The full reference, with request and response schemas, is at /api/docs and the machine-readable OpenAPI 3 document at /openapi.json.

Authenticate with an API key in the Authorization header. Keys are created in a help desk's settings and are scoped to that desk. Widget keys are meant to be embedded in web pages, so they can't read, update or download data.

curl https://intellidesk.co/api/v1/tickets \
  -H "Authorization: Bearer idk_<your-key>"

• /ticketsTickets, messages, internal notes and attachments
• /cardsCards: update, move, comment, complete, attachments
• /projectsProjects, cards, project notes and attachments
• /widgetWebsite widget configuration
• /tagsTags shared by tickets and cards
• /notesProject notes
• /companiesCompanies
• /contactsContacts
• /kbHelp-centre articles
• /time-entriesTime entries and timers
• /timesheetWeekly timesheet submissions
• /time-categoriesTime categories

Register an HTTPS endpoint and choose the events you want. Each delivery is a JSON POST signed with HMAC-SHA256 in the X-IntelliDesk-Signature header (t=<timestamp>,v1=<signature>), with the event name in X-IntelliDesk-Event.

• ticket.created
• ticket.assigned
• ticket.status_changed
• ticket.closed

IntelliDesk runs a Model Context Protocol server, so an MCP client such as Claude Code, Claude Desktop or Cursor can read and work your helpdesk, projects, help centre and timesheets: 75 tools in all.

Endpoint

https://intellidesk.co/api/mcp (Streamable HTTP)

Sign-in

OAuth 2.1 with your IntelliDesk account: the server publishes its authorization server at /.well-known/oauth-protected-resource, so clients start the browser sign-in on their own.

Headless

An MCP API key (idk_mcp_…) as a Bearer token, for scripts and CI. It acts as the person who created it and can use every tool except create_incident, post_incident_update, resolve_incident, which publish to your public status page and need a person's sign-in.

claude mcp add --transport http intellidesk https://intellidesk.co/api/mcp

• AI dev workflow on project cards · 7 toolsBind an AI session to a card, log progress, link PRs.
• Helpdesk · 14 toolsTriage and reply to customer tickets.
• Projects · 16 toolsBoards, cards, notes.
• Customers · 10 toolsContacts and companies.
• Knowledge base · 7 toolsHelp articles.
• Status page · 5 toolsIncidents customers see. Publishing needs a person's sign-in.
• Timesheets · 13 toolsYour time, and submitting it.
• Workspace · 3 toolsWho you are, and the portal's look.

One script tag adds live chat and a request form to your site. It shows chat only while your team is online, can answer from your help articles, and can pass details about the signed-in user to your agents. See live chat.

For language models and AI search: /llms.txt (a short index), /llms-full.txt (the full product reference) and /pricing.md (pricing as Markdown). They're generated from the same data as these pages.