canonical: https://jentic.com/apis/teamhood.com/teamhood

# Teamhood API

Teamhood is a collaborative project management tool for high-performing teams. This API provides access to workspaces, boards, items, attachments, time logs, and more. Rate limited to 100 requests per minute. The API exposes 26 endpoints secured with apiKey authentication.

## For AI agents

Programmatically retrieves attachment metadata by unique identifier.
supports both uploaded file, updates attachment metadata and content by unique identifier.
only supports dir. Covers 26 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Retrieves attachment metadata by unique identifier.
Supports both uploaded file
- Updates attachment metadata and content by unique identifier.
Only supports dir
- Deletes an attachment by unique identifier.
Supports both uploaded files and ex
- Downloads attachment file content by unique identifier.
Only supports directly
- Adds a new attachment to the specified item.
Supports direct file uploads only;
- List Rows by Board Id

## Use cases

### Productivity Operations

Use the Teamhood API to perform productivity operations programmatically. The API provides 26 endpoints covering core functionality including retrieves attachment metadata by unique identifier.
supports both uploaded file, updates attachment metadata and content by unique identifier.
only supports dir, deletes an attachment by unique identifier.
supports both uploaded files and ex.

Example prompt: Call GET /api/v1/attachments/{id} to retrieves attachment metadata by unique identifier.
supports both uploaded file

### Automated Attachments Management

Automate attachments operations by combining multiple Teamhood API endpoints. Agents can updates attachment metadata and content by unique identifier.
only supports dir and then deletes an attachment by unique identifier.
supports both uploaded files and ex in a single workflow.

Example prompt: Call PUT /api/v1/attachments/{id} to updates attachment metadata and content by unique identifier.
only supports dir, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Teamhood API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'retrieves attachment metadata by unique identifier.
supports both uploaded file', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/v1/attachments/{id} | Retrieves attachment metadata by unique identifier. Supports both uploaded file |
| PUT | /api/v1/attachments/{id} | Updates attachment metadata and content by unique identifier. Only supports dir |
| DELETE | /api/v1/attachments/{id} | Deletes an attachment by unique identifier. Supports both uploaded files and ex |
| GET | /api/v1/attachments/{id}/content | Downloads attachment file content by unique identifier. Only supports directly |
| POST | /api/v1/attachments | Adds a new attachment to the specified item. Supports direct file uploads only; |
| GET | /api/v1/boards/{boardId}/rows | List Rows by Board Id |
| GET | /api/v1/boards/{boardId}/statuses | List Statuses by Board Id |
| POST | /api/v1/boards | Create new Board |

## Key resources

- **Attachments** — Manage file attachments on items
- **Boards** — Manage project boards
- **Items** — Manage work items (tasks, stories, etc.)
- **Logs** — Access activity logs
- **Rows** — Manage board rows

## Why Jentic

- **Setup:** Wiring the Teamhood API by hand means provisioning its API key, targeting your workspace-specific host, and building the paging and retry handling for boards, rows, and attachments yourself. Through Jentic you install once, import the Teamhood API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Teamhood API puts the board id in the URL path (/api/v1/boards/{boardId}/rows), so a rule can pin your agent to one board: it can read that board's rows and statuses and nothing else. You choose the operations it may call, so destructive ones like deleting an attachment are not included unless you add them.
- **Credential handling:** Your Teamhood API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list rows on a board' or 'upload an attachment', and Jentic returns the matching Teamhood API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Teamhood API use?

The Teamhood API uses an API key passed in the `X-ApiKey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I retrieves attachment metadata by unique identifier.
supports both uploaded file with the Teamhood API?

Yes. Use the GET /api/v1/attachments/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Teamhood API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I retrieves attachment metadata by unique identifier.
supports both uploaded file through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieves attachment metadata by unique identifier.
supports both uploaded file'. Jentic returns the matching Teamhood API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Teamhood API have?

The Teamhood API exposes 26 endpoints covering attachments, boards, items operations.

### Can I limit what my agent is allowed to do with the Teamhood API?

Yes. Because you run Jentic One yourself, you decide which Teamhood operations and credentials your agent may use, and your own rules are enforced at execution time. Since the Teamhood API carries the board id in the URL path (/api/v1/boards/{boardId}/rows), you can pin the agent to a single board so it only reads that board's rows and statuses. You also choose the exact operations it may call, so destructive ones such as deleting an attachment are excluded unless you explicitly grant them.