Api Sxkan78ybekjjaveh1lcig Teamhood Teamhood API v1

Name: Teamhood API v1 API
Brand: Teamhood API
Availability: InStock

✓ Official Vendor SpecProductivityTask ManagementapiKey26 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Teamhood API v1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Teamhood API v1, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi-sxkan78ybekjjaveh1lcig.teamhood.com%2Fteamhood" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi-sxkan78ybekjjaveh1lcig.teamhood.com%2Fteamhood" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Teamhood API v1 API.

List, read, and structure boards including their rows and statuses to mirror the Teamhood UI in code

Read and update individual work items on a board including their status and assignment

Attach files to a work item by uploading via /api/v1/attachments and referencing the returned id

GET STARTED

Start building with Teamhood API v1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Teamhood API v1 API for, with concrete tasks.

★ Sync Teamhood Boards with External Tools

Build a one-way or two-way sync between Teamhood and another tool such as a CRM or a code repository by listing boards, walking their rows and items, and reflecting state changes through the items endpoints. The board, row, and status endpoints provide the structural metadata needed to map Teamhood's hierarchy into the external system. Activity feeds give a delta to drive incremental sync.

List boards via /api/v1/boards, then for each board call /api/v1/boards/{boardId}/rows and /api/v1/boards/{boardId}/statuses to build a structural map

Attach Documents to Work Items

Programmatically attach generated reports, screenshots, or contracts to Teamhood items by uploading through /api/v1/attachments and referencing the returned attachment id on the item. The /api/v1/attachments/{id}/content endpoint then lets downstream tools fetch the file when reviewing the item. This is useful when an agent produces an artefact that needs to live alongside a task.

POST a generated PDF to /api/v1/attachments, capture the id, and update the related Teamhood item to reference the attachment id

Activity Audit Trail

Pull recent item activities with /api/v1/boards/{boardId}/item-activities to feed a compliance log, an executive dashboard, or a Slack digest of board changes. The endpoint returns the structured activity feed for the board, which can then be filtered by user, item, or change type before forwarding downstream.

Call /api/v1/boards/{boardId}/item-activities with a recent since-timestamp, filter for status changes, and post a digest to a Slack channel

Agent Integration via Jentic

An AI agent built on Jentic can search for Teamhood board, item, and attachment operations by intent and execute them without holding the X-ApiKey in agent context. Jentic's your Jentic One instance holds the credential and returns scoped access at call time, which is helpful when an agent automates work across multiple project tools.

Use Jentic search for 'list teamhood boards', load the /api/v1/boards operation, execute it, and pass the returned board ids into a follow-up rows call

Key Endpoints

26 endpoints — teamhood is a project and task management platform exposing a v1 rest api that covers boards, rows, items, statuses, attachments, and item activity feeds.

METHOD

PATH

DESCRIPTION

GET

/api/v1/boards

List boards in the workspace

GET

/api/v1/boards/{boardId}/rows

List rows on a board

GET

/api/v1/boards/{boardId}/statuses

List the status columns configured on a board

GET

/api/v1/boards/{boardId}/item-activities

Pull the item activity history for a board

GET

/api/v1/items/{itemId}

Read a single work item

POST

/api/v1/attachments

Upload an attachment for linking to an item

GET

/api/v1/attachments/{id}/content

Download an attachment by id

GET

/api/v1/boards

List boards in the workspace

GET

/api/v1/boards/{boardId}/rows

List rows on a board

GET

/api/v1/boards/{boardId}/statuses

List the status columns configured on a board

GET

/api/v1/boards/{boardId}/item-activities

Pull the item activity history for a board

GET

/api/v1/items/{itemId}

Read a single work item

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Teamhood API by hand means handling its X-ApiKey header, targeting your tenant host, and mapping the board, item, attachment, and activity routes yourself. Through Jentic you install once, import Teamhood from the API Directory, store the key once, and your agent calls it.

Permission scoping

Teamhood puts the board id in the URL path (/api/v1/boards/{boardId}/rows, /api/v1/boards/{boardId}/statuses), so a rule can pin your agent to one board: it can read that board's rows, statuses, and activity and nothing else. You choose the operations it may call, so uploading attachments is only included if you add it.

Credential isolation

Your Teamhood X-ApiKey is stored once, encrypted, by your own Jentic One instance and injected as the header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Teamhood boards' or 'upload an attachment to a Teamhood item', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Teamhood API v1 API through Jentic.

What authentication does the Teamhood API use?

Teamhood requires an API key passed as the X-ApiKey header. Through Jentic the key is held in your Jentic One instance and a scoped execution token is granted at call time, so the agent never holds the raw key.

Can I attach files to Teamhood items via the API?

Yes. POST a file to /api/v1/attachments, capture the returned attachment id, and reference it on the related item. Use GET /api/v1/attachments/{id}/content to retrieve the file when reviewing the item later.

What are the rate limits for the Teamhood API?

Teamhood limits requests to 100 per minute per API key. Stay within that ceiling, batch reads where possible, and respect any 429 responses with exponential backoff.

How do I list a workspace's boards through Jentic?

Install the Jentic SDK with pip install jentic, search for 'list teamhood boards', load the GET /api/v1/boards operation, and execute it. Run it through Jentic One, the self-hosted execution layer to get a Jentic agent key.

Can I get the activity history for a board?

Yes. GET /api/v1/boards/{boardId}/item-activities returns the item activity feed for a board, which you can filter by since-timestamp or user to produce digests, audit logs, or change notifications.

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

Yes. Because you run Jentic One yourself, your own rules decide which Teamhood operations and credentials the agent may use. Teamhood puts the board id in the URL path, such as /api/v1/boards/{boardId}/rows and /api/v1/boards/{boardId}/statuses, so a rule can pin the agent to a single board and let it read only that board's rows, statuses, and activity. You also pick the exact operations it can call, so uploading files through /api/v1/attachments is included only if you add it.