Backend API workflow response headers

[orth.dev.38]

The Content-Type in bubble’s API response is content-type: application/json.
But we need content-type: application/json;charset=utf-8

Would be nice to have an additional parameter in ‘Return data from API’ action as list of key-value to specify nedded headers

Other

How do I return XML via an API workflow?

The return data to API function needs to have headers as well as parameters. Would solve many problems and limitations.

Is it possible to send a dynamic key in header of API Workflow?

There is a service that I’d like to use that requires an auth token to be sent in the header of every request. That auth token expires after an arbitrary period of time (let’s say an hour). How can I set up an API Workflow to store an auth token, and then use that stored auth token in the header of an API call thru Bubble?

The best way to build web apps without code | Bubble

[aj11]

This is an incredibly annoying issue that has been ignored for a very long time. I can’t imagine it’d be that complicated to add since they already allow switching to “content-type: plain/text” via the checkbox. All they need to do is add a field that allows you to enter the content type of your choice. It would solve so many issues around interacting with outside APIs.

@josh @nickc Is there any hope for us advanced Bubbles when it comes to adding this?

I mocked up a UI for this feature that can be found here: Feature Request: 'Return Data from API' More Content Type Options

[gaimed]

You can do it with coalias.com in a couple of weeks. At headers to only specific urls

[aj11]

I’ll check it out. It will be live soon?

[gaimed]

Almost. In two weeks.

[orth.dev.38]

@gaimed

Almost. In two weeks.

two minutes turkish

[gaimed]

Bubble released a fix. You can now do it inside bubble.