We just deployed an improvement for the API connector that lets you define some dynamic parts in the URL (an the body for a POST request). If you enter part of the body between brackets (“[xx]”), Bubble will automatically
identify this as a parameter
replace it in run mode / initialization call by the value.
It’ll work as parameters for the body of the request, if you mark them private that means they can’t be modified at the call level, while if they’re not private you can change them at the action or the Get data from API level.
This implementation will make that users don’t have to deal with URLs, etc, and it more powerful in the long run.
As usual, let us know if you hit issues through a bug report.
Can you please provide the appropriate syntax for me? I have tried filling in the value, filling in with quotes, removing the “Johnnyboy” from the body, and 40 other variations. With no luck. Can you please explain how this call should be written when using the feature?
That’s a good question (and good point…). Turns out [] isn’t great for body, but works great for the URL. We’ll change that to <> in the body, that should be safer and you’ll still be able to use arrays, etc.
In terms of quotes, it’s your responsibility to make it work. What we do is just replace the by hello (if the value is hello).
Issue with the new syntax “”. The API connectors don’t seem to be picking the value. Even in the Modify Call action the values are not being fed in. Any fix?
Also, what happens to all the earlier established API connectors? Do they auto adjust or do we have change all of them manually?
Done. Also, anyway is it possible to do limited release of new features? Over the past few days there had been 2 updates on this i think, and we had to redo all initializations for API calls. Was pretty frustrating given we had a lot of these calls.
Bubble, can you please make a tutorial about connecting twitter external API, so I can POST, GET on behalf of my users. I love the tutorial you made on how to use the Etsy API but it wasn’t enough to make me understand how to POST using Twitter API because it’s more complex.