Forge Fetch API not supporting content type application/x-www-form-urlencoded in POST?

Should it be possible to make POST requests using the Forge Fetch API with content types other than “application/json”? I tried with {‘Content-Type’: ‘application/x-www-form-urlencoded’} as the headers property of the fetch options object, but this seems to be ignored.
If it is indeed not possible, do you plan to extend to other content types?

1 Like

Hey @UdoHagemannDecadisAG,

We have identified the underlying issue and are currently working on allowing other content types.


Hi @UdoHagemannDecadisAG, this is fixed in the latest release. See Web trigger API updates, CLI improvements, and bug fixes for more info.