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

# Trello

This document describes the REST API of Trello as published by Trello.com. - <a href='https://trello.com/docs/index.html' target='_blank'>Official Documentation</a> - <a href='https://trello.com/docs/api' target='_blank'>The HTML pages that were scraped in order to generate this specification.</a>. The API exposes 324 endpoints secured with apiKey authentication.

## For AI agents

Programmatically getactionsbyidaction(), updateactionsbyidaction(). Covers 324 operations with apiKey authentication.

## Scope

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

## Capabilities

- getActionsByIdAction()
- updateActionsByIdAction()
- deleteActionsByIdAction()
- getActionsBoardByIdAction()
- getActionsBoardByIdActionByField()
- getActionsCardByIdAction()
- getActionsCardByIdActionByField()

## Use cases

### E-Commerce Operations

Use the Trello to perform e commerce operations programmatically. The API provides 324 endpoints covering core functionality including getactionsbyidaction(), updateactionsbyidaction(), deleteactionsbyidaction().

Example prompt: Call GET /actions/{idAction} to getactionsbyidaction()

### Automated action Management

Automate action operations by combining multiple Trello endpoints. Agents can updateactionsbyidaction() and then deleteactionsbyidaction() in a single workflow.

Example prompt: Call PUT /actions/{idAction} to updateactionsbyidaction(), then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Trello 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 'getactionsbyidaction()', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /actions/{idAction} | getActionsByIdAction() |
| PUT | /actions/{idAction} | updateActionsByIdAction() |
| DELETE | /actions/{idAction} | deleteActionsByIdAction() |
| GET | /actions/{idAction}/board | getActionsBoardByIdAction() |
| GET | /actions/{idAction}/board/{field} | getActionsBoardByIdActionByField() |
| GET | /actions/{idAction}/card | getActionsCardByIdAction() |
| GET | /actions/{idAction}/card/{field} | getActionsCardByIdActionByField() |
| GET | /actions/{idAction}/display | getActionsDisplayByIdAction() |

## Key resources

- **action** — https://trello.com/docs/api/action/index.html
- **batch** — https://trello.com/docs/api/batch/index.html
- **board** — https://trello.com/docs/api/board/index.html
- **card** — https://trello.com/docs/api/card/index.html
- **checklist** — https://trello.com/docs/api/checklist/index.html

## Why Jentic

- **Setup:** Wiring the Trello API by hand means passing both its key and token query parameters on every call to trello.com/1 and handling error responses yourself. Through Jentic you install once, import Trello from the API Directory, store the key and token once, and your agent calls it.
- **Permission scoping:** Trello puts the action id in the URL path (/actions/{idAction}), so a rule can pin your agent to one action: it can read that action and its board or card and nothing else. You choose the operations it may call, so updating or deleting an action is not included unless you add it.
- **Credential handling:** Your Trello key and token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get an action by id' or 'find the board for an action', and Jentic returns the matching Trello operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Trello use?

The Trello uses an API key passed in the `key` query. 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 getactionsbyidaction() with the Trello?

Yes. Use the GET /actions/{idAction} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Trello?

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 getactionsbyidaction() through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getactionsbyidaction()'. Jentic returns the matching Trello operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Trello have?

The Trello exposes 324 endpoints covering action, batch, board operations.

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

Yes. Because you run Jentic One yourself and your own rules decide which operations and credentials the agent may use, you pick exactly which Trello calls it can make. Trello puts the action id in the URL path (/actions/{idAction}), so a rule can pin the agent to one action, letting it read that action and its board or card and nothing else. Since you choose the operations, updating or deleting an action is not available to the agent unless you add it.