Is there a way to balance api body parameter "dynamic" and "private"?

I am using Bubble’s API feature, where I dynamically add some data to the body parameter in workflows.

This implies that I must disable the private option for the body parameter.

However, for certain considerations, I also want to maintain the privacy of the body parameter.

Is there a way to balance “dynamic” and “private”?

Maybe call the API in backend workflow? so you could access and pass private data dynamically in a secured way

1 Like

Good idea.I made it !

1 Like