Trello API
GET /application/:id/compliance/memberPrivacy endpoint removal
Stopped workingSubscribe to Trello APIShare
Calls to GET /application/:id/compliance/memberPrivacy on Trello API stopped working on September 8, 2025.
Calls it hits
GET /application/:id/compliance/memberPrivacy
What to use instead of these calls
Use the /plugin/:id/compliance/memberPrivacy API instead, which provides similar functionality and is required for ongoing compliance.
In Trello API's words
The legacy /application/:id/compliance/memberPrivacy API route will be deprecated and removed after Sep 8, 2025 .
Facts
- API
- Trello API
api.trello.com - Kind
- Endpoint removal
- Takes effect
- September 8, 2025
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Trello API's own pages
Questions
When does this change take effect?
Calls to GET /application/:id/compliance/memberPrivacy on Trello API stopped working on September 8, 2025.
What happens to calls after September 8, 2025?
They have failed since September 8, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Trello API 4
-
PUT /1/boards/{id}/myPrefs/showListGuideEndpoint removal Stopped working -
GET /1/application/{id}/compliance/memberPrivacyEndpoint removal Stopped working -
GET /1/applications/{id}/compliance/memberPrivacyEndpoint removal Stopped working -
No date
PUT /1/boards/{id}/labelNames*Endpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.