Trello API
PUT /1/boards/{id}/labelNames* endpoint removal
Deprecated, no dateSubscribe to Trello APIShare
Trello has deprecated PUT /1/boards/{id}/labelNames* without providing a specific shutdown date. Trello API noted that this endpoint will be deprecated in 6 months per developer guidelines. After removal, affected calls to this endpoint fail.
Calls it hits
PUT /1/boards/{id}/labelNames*
What to use instead of these calls
Create labels using POST /1/boards/{idBoard}/labels or POST /1/labels, and rename existing labels using PUT /1/labels/{id}.
In Trello API's words
This endpoint will be deprecated in 6 months per our developer communications guidelines (August 18, 2025).
Facts
- API
- Trello API
api.trello.com - Kind
- Endpoint removal
- Announced
- February 17, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Trello API's own pages
Questions
When does this change take effect?
Trello API deprecated PUT /1/boards/{id}/labelNames* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Trello API has not given a shutdown date yet.
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 /application/:id/compliance/memberPrivacyEndpoint removal Stopped working -
GET /1/application/{id}/compliance/memberPrivacyEndpoint removal Stopped working -
GET /1/applications/{id}/compliance/memberPrivacyEndpoint removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.