Atlassian Release Notes

Trello now supports OAuth 2.0 authorization code grants for apps, featuring granular scopes, short-lived tokens, resource restrictions, and a redesigned consent screen consistent with other Atlassian products. New apps can opt in right away, and existing apps can transition when ready.

Read more on our developer community page - OAuth 2.0 is now available for Trello!

The legacy /application/:id/compliance/memberPrivacy API route will be deprecated and removed after 08 Sep 2025. This change is part of ongoing efforts to simplify our codebase and align with current privacy practices for Trello power-ups and integrations.

This endpoint is no longer referenced in our API documents or guides and the showListGuide board preference is no longer used throughout the application. We will begin to remove this route after 26 Jul 2025.

The markdown parser for global power-ups directory has been updated. These changes are also reflected in the Trello card editor. We recommend reviewing your Power-Up listings to ensure your markdown displays as expected. If you need to make adjustments, check out how to format text in Trello.

• Support for establishing a websocket connection via appkey+token pairs supplied via query arguments will end on November 15, 2024.

• While this continues to be undocumented and unsupported, you may make Websocket connections to Trello, however you will need to switch to providing an OAuth Authorization header for authentication.

  • Note that this isn’t possible in the browser sandbox environment, as the WebSocket API does not have an option to provide custom HTTP headers.

  • You will need to do this from a privileged context, like an app or possibly a browser add-on in the Trello session context.

Up until now, a card’s idShort field value would be restored to its previous value when the card is moved to a board it has previously been on.

Starting 01 Aug 2024 this will no longer be the case. idShort will always receive a new sequence ID on the destination board. This will have no impact on existing idShort values, or on idShort values on cards moved within a single board.

As of July 17, 2024, you no longer need to contact Trello to change your public Power-Up Iframe Connector Url domain. You can self-serve this change by going to trello.com/power-ups/admin, selecting your Power-Up, and updating the Iframe connector URL field in Basic information.

While disabling power-up, you can now select Keep all Power-Up data to opt-in to retain the plugin data stored on the board and cards.

Attached file

Rollout completed March 12th 2024

Trello’s API will no longer permit supplying a body with a GET request. Previous behavior in our API ignored the payloads provided with GET requests but these requests will now be blocked with a 403 response from our content delivery network.

To resolve issues resulting from this change ensure all GET requests to Trello’s API are sent without a payload.

Trello has introduced a /w/ and /u/ route prefix for workspace and member routes. This change has already been rolled out, with API responses for workspaces (or “organizations” in the API) and members returning the prefixed url values.

Trello will cease support for the legacy format by 08 Aug 2024 and as such all integrations storing URLs must update to the new format by that date.

In addition to the action and the model fields, webhook event responses now contain the webhook field, which contains the webhook model itself. The webhook model fields are id, active, callbackURL, description, idModel, consecutiveFailures, firstConsecutiveFailDate.

See our webhook documentation for full details on webhook event responses.

We currently disable webhooks when they “fail” consecutively for 30 days without recovering. Previously, the only type of “failure” was when the webhook callback endpoint returned something other than a 200 response when a webhook event was sent. With this change, webhook events failing because its token lost access to the webhook's model is now considered a failure, and will count towards disablement if not fixed within 30 days.

API responses for custom field items will now include value and idValue fields with a null value, rather than omitting the fields depending on the custom field type, to maintain consistent API response shapes.

Workspaces that own publicly listed Power-Ups can no longer be deleted. This will prevent those Power-Ups from breaking for other users that have them installed. Users need to remove all publicly listed Power-Ups from a workspace before deleting it.