> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/trello.md).

# Trello

## OAuth app properties

The Trello connector uses Trello's OAuth 1.0 flow with an API key and its secret. The key belongs to a Power-Up (an app) in the Trello admin portal.

| Property                | Value                                                                                                                                                                                            |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Multi-tenant**        | **Yes.** Any Trello user can authorize one API key.                                                                                                                                              |
| **Vendor review**       | **None.** Listing a public Power-Up is optional and not needed for the REST API.                                                                                                                 |
| **Review time**         | Not applicable.                                                                                                                                                                                  |
| **Users before review** | No limit.                                                                                                                                                                                        |
| **App owner**           | An admin of a Trello Workspace. The Power-Up is created for that Workspace at [trello.com/apps/admin](https://trello.com/apps/admin), and the API key and secret are on its **Trello Auth** tab. |
| **Regions**             | One key works for all Trello users.                                                                                                                                                              |
| **Client secret**       | No expiry documented. The secret is on the **Trello Auth** tab next to the API key.                                                                                                              |
| **Rate limits**         | 300 requests per 10 seconds per API key, shared by all your users. 100 requests per 10 seconds per token. 100 requests per 900 seconds on `/1/members/`.                                         |
| **Checked**             | 2026-11-13                                                                                                                                                                                       |

**Limitations**

* The API key quota is shared by every account connected through it. When the key gets more than 200 `429` responses within 10 seconds, Trello rejects all its remaining requests in that window.
* The connector requests the `read`, `write` and `account` scopes with `expiration=never`, so the token does not expire. It stops working only when the user revokes it in Trello.
* Trello redirects back only to an origin listed under the key's **Allowed origins** (Trello Auth tab), and a key with no allowed origins blocks every redirect. Add your Appmixer API URL there, for example `https://api.acme.appmixer.cloud`.
* Trello added OAuth 2.0 (3LO) on 2026-09-15 and recommends it for new apps. The connector still uses OAuth 1.0, which Trello supports with no deprecation date.

Sources: [Authorizing with Trello's REST API](https://developer.atlassian.com/cloud/trello/guides/rest-api/authorization/), [Managing apps](https://developer.atlassian.com/cloud/trello/guides/power-ups/managing-apps/), [Rate limits](https://developer.atlassian.com/cloud/trello/guides/rest-api/rate-limits/), [Trello changelog](https://developer.atlassian.com/cloud/trello/changelog/). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Backoffice configuration

Configuration ID: `appmixer:trello` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `consumerKey` — API key of the Trello Power-Up (**Trello Auth** tab at [trello.com/apps/admin](https://trello.com/apps/admin)).
* `consumerSecret` — Secret of the same API key, on the same tab.
* `name` — Optional. The app name Trello shows on its authorization page. Default `Appmixer`.
* `outputFilePrefix` — Optional. File name prefix of the CSV file that **ListBoards**, **ListBoardsCards**, **ListBoardsList**, **ListBoardsMembers**, **ListBoardLabels**, **ListCardLabels**, **ListCardChecklists** and **ListChecklistItems** create when their output is set to a file; the file is named `<prefix>-<component name>.csv`. Default `trello-export`.

![Setting the OAuth page name in the Backoffice](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-224be76043830d1377a22dca8a34008371774c6d%2Ftrello-1.png?alt=media)

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-361e16c4b1200d20910634ed16cb847fd75bd994%2Ftrello-2.png?alt=media)

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:trello -u -d '{
  "consumerKey": "<api key>",
  "consumerSecret": "<api secret>",
  "name": "<app name>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/trello.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
