Teamwork API
Provides programmatic access to Teamwork's project management platform including projects, tasks, milestones, time tracking, messages, files, and billing via REST API with API key or OAuth2 authentication.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
OAuth2 with scopes is the preferred auth method and limits blast radius. API key via Basic auth is less ideal. SOC 2 Type II certified. GDPR compliance with EU data residency option.
⚡ Reliability
Best When
You need to automate project creation, task management, and time logging in a client-services or agency delivery context where Teamwork is the system of record.
Avoid When
Your team uses agile/scrum workflows and needs sprint planning, story points, and burndown charts — tools like Jira or Linear are better suited.
Use Cases
- • Create tasks and assign them to team members programmatically when triggered by external events (e.g., new support ticket, form submission, CRM deal stage change)
- • Log time entries against specific tasks or projects from an external time tracking or invoicing tool via automated sync
- • Query all overdue milestones across active projects to generate a daily executive summary report for a status reporting agent
- • Sync project and task status from Teamwork into an external dashboard or reporting database on a scheduled basis
- • Automatically create a new project with a predefined task list template when a new client is onboarded in the CRM
Not For
- • Real-time collaborative editing of documents or tasks — Teamwork uses async API patterns, not live collaboration sockets
- • Agile-specific workflows like sprint boards or story points — Teamwork is better suited to client-facing project delivery than Scrum teams
- • Advanced resource capacity planning beyond basic time tracking
Interface
Authentication
Supports both API key (HTTP Basic auth with the key as username and 'x' as password) and OAuth2 authorization code flow for user-delegated access. OAuth2 supports scopes for limiting access.
Pricing
Free plan API access is useful for development and small teams. Paid plans unlock more projects, storage, and advanced features like invoicing and reports.
Agent Metadata
Known Gotchas
- ⚠ Teamwork has multiple API versions (v1, v2, v3) with different endpoint paths and response formats — always specify the version and use a consistent version throughout
- ⚠ POST requests on create endpoints are not idempotent — network retries can create duplicate tasks, projects, or time entries without external deduplication
- ⚠ The site URL prefix varies per account (e.g., yoursite.teamwork.com) — agents must store and use the account-specific base URL, not a generic hostname
- ⚠ Webhook event payloads are not versioned and can change without notice — build defensive parsing for webhook consumers
- ⚠ API key authentication uses HTTP Basic auth with the key as username — this is easy to misconfigure; ensure the password field is set to 'x' as documented
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Teamwork API.
Scores are editorial opinions as of 2026-03-06.