Trello REST API regression: /cards/{id}/actions and /boards/{id}/actions returning 500

[David Carter]

 # Trello REST API: `GET /cards/{id}/actions` returning 500 (unannounced)

**Endpoint affected:** `GET /1/cards/{id}/actions` (with or without `filter=` param) and `GET /1/boards/{id}/actions`

**Symptom:** Consistent HTTP 500 "Internal Server Error" since at least 11:00 BST on 2026-05-18. Not announced on status.atlassian.com.

**Scope of impact:** This is the only way to read comment history on a card via the REST API. Any tooling that watches Trello card comments (workflow automation, custom integrations, the `@delorenj/mcp-server-trello` package, anything reading `commentCard` actions) is broken.

## Repro

Using a valid API key + token:

```bash

# Sanity — these work fine, so it's not credentials or general outage

curl -sw "%{http_code}\n" -o /dev/null \

  "https://api.trello.com/1/members/me?key=$KEY&token=$TOKEN"

# → 200

curl -sw "%{http_code}\n" -o /dev/null \

  "https://api.trello.com/1/cards/{anyCardId}?key=$KEY&token=$TOKEN"

# → 200

# But:

curl -sw "%{http_code}\n" \

  "https://api.trello.com/1/cards/{anyCardId}/actions?filter=commentCard&key=$KEY&token=$TOKEN"

# → 500 Internal Server Error

curl -sw "%{http_code}\n" \

  "https://api.trello.com/1/cards/{anyCardId}/actions?key=$KEY&token=$TOKEN"

# → 500 Internal Server Error (no filter — still broken)

curl -sw "%{http_code}\n" \

  "https://api.trello.com/1/boards/{anyBoardId}/actions?filter=commentCard&key=$KEY&token=$TOKEN"

# → 500 Internal Server Error

```

Inline workaround (`GET /1/cards/{id}?actions=commentCard&actions_limit=5`) returns HTTP 449 with `"actions": []` — also non-functional.

## Cards tested

Multiple cards across different boards under my account. Reproducible on every card, not card-specific.

## What I'd like to know

1. Is this a known regression? It's not on status.atlassian.com.

2. Is there a workaround endpoint for reading card comments while this is broken?

3. ETA on restoration?

Happy to provide additional logs or test against a specific card on request.

[Arkadiusz Wroblewski]

Hello @David Carter 

Trello is currently experiencing an active outage, so a 500 error is not surprising. Please be patient; Atlassian is working hard to address this issue.

https://trello.status.atlassian.com/

[David Carter]

Thanks for the guidance