Custom Action limitation with application/x-www-form-urlencoded payloads (Twilio WhatsApp case) | Community
Skip to main content
Silvio6
Level 5
January 27, 2026
Solved

Custom Action limitation with application/x-www-form-urlencoded payloads (Twilio WhatsApp case)

  • January 27, 2026
  • 1 reply
  • 20 views

Hi,

I’m trying to call the Twilio Messages API (WhatsApp) from a Custom Action.

Twilio requires application/x-www-form-urlencoded POST bodies (To, From, Body in the request body).


However, in Custom Actions, even when the content type is set to application/x-www-form-urlencoded, the payload appears to be sent as JSON or query parameters, not as a true form-encoded body.

 

This results in Twilio errors like:
21604 – A 'To' phone number is required

The exact same request works via curl and Python (requests.post(data=...)) but fails from AJO.

  • Is it a known limitation that Custom Actions don’t support true x-www-form-urlencoded bodies?
  • Are there plans to support non-JSON request bodies?

Thanks!

Best answer by SatheeskannaK

@Silvio6 

(AJO) currently only supports the content-type: application/json. I haven’t seen anything for non-JSON requests is not included in the feature roadmap. It would be beneficial to submit this as an enhancement request.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/action-journeys/about-custom-action-configuration#custom-actions-limitations

 

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity AdvisorAccepted solution
Community Advisor
January 27, 2026

@Silvio6 

(AJO) currently only supports the content-type: application/json. I haven’t seen anything for non-JSON requests is not included in the feature roadmap. It would be beneficial to submit this as an enhancement request.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/configure-journeys/action-journeys/about-custom-action-configuration#custom-actions-limitations

 

Thanks, Sathees