Skip to main content
Question

Support for form data in FME Data Virtualization endpoints

  • September 2, 2025
  • 3 replies
  • 62 views

jipx
Contributor
Forum|alt.badge.img+16
  • Contributor
  • 5 replies

Is there any plan to support receiving data in application/x-www-form-urlencoded with FME Data Data Virtualization endpoints?

 

Currently, when creating an endpoint, the request body only allows application/json as the content type. In some cases, external applications or services can only send form-encoded data rather than JSON.

 

Is support for form data planned in upcoming versions?

3 replies

nia.colebrooke
Safer
Forum|alt.badge.img+4
  • Safer
  • 11 replies
  • September 9, 2025

Hi jipx,

 

We are currently working to increase the content type options for data virtualization request bodies. Unfortunately, application/x-www-form-urlencoded is currently considered out of scope.

 

If you wouldn’t mind sharing a bit more about your use case for this MIME type, I will include it in our internal conversations.


jipx
Contributor
Forum|alt.badge.img+16
  • Author
  • Contributor
  • 5 replies
  • September 10, 2025

I was planning to replace an old (v8.11.2) Node.js API with FME Data Virtualization. The challenge is that the application sending data to the specific API uses the application/x-www-form-urlencoded format for requests. I know that I can receive this type of data with a regular workspace, but it would have been perfect if everything could be handled within the same data virtualization API.


nia.colebrooke
Safer
Forum|alt.badge.img+4
  • Safer
  • 11 replies
  • September 10, 2025

Thank you for sharing that with us. We’ve created an internal ticket to track this feedback and will reconsider adding support for this MIME type in a future version.