Twilio Content API
allow_category_change body parameter behaviour change on POST /v1/Content/{id}/ApprovalRequests/whatsapp
Deprecated, no dateSubscribe to Twilio Content APIShare
Twilio Content API deprecated POST /v1/Content/{id}/ApprovalRequests/whatsapp, body parameter allow_category_change without giving a shutdown date yet.
Calls it hits
POST /v1/Content/{id}/ApprovalRequests/whatsappbody parameter allow_category_change
What to use instead of these calls
Drop allow_category_change; WhatsApp may now reclassify a template's category, so choose the category its content fits.
In Twilio Content API's words
We have now unpublished this field from our documentation as it will no longer function. API calls with this field will still submit the template for approval but will no longer prevent recategorizations.
Facts
- API
- Twilio Content API
content.twilio.com - Kind
- Behaviour change
- Announced
- April 25, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Twilio Content API's own pages
Questions
When does this change take effect?
Twilio Content API deprecated POST /v1/Content/{id}/ApprovalRequests/whatsapp, body parameter allow_category_change without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Twilio Content 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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.