Every tool definition rides along on every turn, so connecting to the root URL means paying for ticketing tools while you manage projects. The role profiles solve exactly that, and choosing one is the single highest-value decision when connecting this. The permission defaults are sensible in a way worth noting too: writes on, deletes off everywhere, with a read-only switch for organisations that want analysis without action. Deletes being unavailable rather than merely discouraged is the right kind of guardrail.
Teamwork's endpoint spans four products, and the tool count reflects it. Rather than making you take all of it, they publish role-scoped profile endpoints that expose a subset.
- Projects — tasks and tasklists, projects, comments, timelogs, workflow stages, activity feeds
- A cross-entity keyword search over projects, tasks, files and messages
- Desk tickets, Spaces and Chat, each under their own tool prefix
- Profile endpoints — project manager, support, desk, analyst, knowledge manager and ops — each a narrower slice
- OAuth 2 with per-product scopes, or a bearer API token
- An admin can leave it disabled site-wide from the AI setting
- Writes are enabled by default; deletes are disabled everywhere; a read-only mode exists for restricted deployments
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen