SAP Knowledge Base Article - Preview

3621755 - Twilio January 2026 impact assessment : twilio Authy api update on get requests with body

Symptom

June 2025: Notification from Twilio SMS Provider

Summary of the Update:

Deadline Extended: GET Requests With Body for Authy API Now Rejected on Jan 15, 2026

Ahoy!

On May 8, 2025, Twilio sent an advisory to some customers outlining an upcoming change to the Twilio Verify V1/Authy API endpoints. This change, initially planned for June 16, 2025, would stop accepting GET requests that include a request body. The goal is to enhance security and better protect against smuggling attacks.

To ensure a smooth transition and give customers more time to update their integrations, Twilio is extending the deadline for this change to January 15, 2026.

What customers need to do:

  • Update any GET requests that include a request body to either remove the body or use the correct HTTP method (such as POST).
  • If third-party integrations are involved, confirm with those providers to ensure they are aware of and preparing for this change.

Thank you for building with Twilio! 


Read more...

Environment

  • SAP Customer Data Cloud
  • SMS Provider- Twilio

Product

SAP Customer Data Cloud all versions

Keywords

Gigya , KBA , CEC-PRO-SYS , System (Network, Performance, SMTP, Rate Limits, Latency) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.