API Instability and Errors with wrong status-code/no response

[Rasmus Wulff Jensen]

For the last week or so, I’ve seen an increasing number of errors from the Trello REST API. The errors are kind of odd as they are HTTP 202 Accepted status codes, but with blank error messages (HTTP.Response is an empty string), instead of the normal 200 OK Status code

It is very sporadic, with all requests failing for 3-5 minutes and then working again for hours. Nothing has been changed on the consuming end, and no incidents are posted on the Trello Status site

Anyone else using the Trello API is seeing something similar?

[Lara · Accepted solution]

Hi all, @Rasmus Wulff Jensen @Tanay Patwa @Daniel Fairhead @Gabriel Cullen 

Thanks for your reports.

Our engineering team investigated this and reverted a change made to the API, which should have resolved the issue.

Would you mind performing a request on your side and confirming? Thanks!

Lara

[Tanay Patwa]

im having the same issue and its really frustrating as we use these APIs in production for our business.

And the issue is its so random. most times it will work

[Daniel Fairhead]

We're also having the same issue.

[Gabriel Cullen]

We're getting the exact same problem

[Vitalii Rybka]

Hey Rasmus,

That's definitely odd behavior HTTP 202 with empty responses is not normal for the Trello API. A few things come to mind:

First, you're not alone I've seen similar reports pop up in various dev communities over the past week or two. The intermittent nature (failing for 3-5 minutes then working for hours) suggests it's likely on Trello's side rather than your implementation.

Potential causes:

• Infrastructure changes/updates on Trello's end that aren't being communicated
• Load balancer issues routing to unhealthy backend instances
• Rate limiting implementation changes (though 202 would be weird for that)
• CDN/proxy layer problems

What you can do:

1. Log everything  capture timestamps, specific endpoints, request patterns when it happens
2. Retry logic if you don't already have exponential backoff, now's a good time
3. Monitor pattern see if it correlates with specific times of day or request types
4. Report it  even though status page is clean, file a support ticket with Trello. Include your logs and mention the HTTP 202 specifically

The fact that the status page isn't showing anything is frustrating but not uncommon - sometimes these infrastructure hiccups don't trigger their monitoring thresholds.

Have you tried hitting different endpoints to see if it's global or specific to certain API routes?

Would love to hear if others are seeing this too. Drop me a line if you want to compare notes on the patterns you're seeing

[Rasmus Wulff Jensen]

Support Ticket already filed (awaiting response)...I Have retry logic and logging in place but retry currently do not treat 202 as a retry scenario so need to adjust that temporarily.