Hello
When Bubble reads a dynamic value from the API, it's changing the value before executing the connection.
Observe in the screenshot of the step-by-step sequence. The value of the dynamic parameter CUSTOMER is read correctly until the last step of the workflow. Why is the company ASAAS rejecting the value (e.g., cus_000007514049)?
The call with the fixed values was successfully initialized. The data exists in the Asaas DB.
Can you check if there's a problem with the API? I can't find anything.
I know it's a simple thing, but I've been trying for 3 days and I can't find the problem.
Thank you very much for your help.
Hello
When Bubble reads a dynamic value from the API, it's changing the value before executing the connection.
Observe in the screenshot of the step-by-step sequence. The value of the dynamic parameter CUSTOMER is read correctly until the last step of the workflow. Why is the company ASAAS rejecting the value (e.g., cus_000007514049)?
The call with the fixed values was successfully initialized. The data exists in the Asaas DB.
Can you check if there's a problem with the API? I can't find anything.
I know it's a simple thing, but I've been trying for 3 days and I can't find the problem.
Thank you very much for your help.
1 Like
First, use dynamic value directly in API connector if possible with placeholder.
After, in fields that this will create, be sure to set the correct value.Actually, because you are setting the JSON in the dynamic box, this will add new line and encode it. This break the JSON.
Another solution is to set the JSON as a single line string instead in the JSON box.
@nick.carroll This could be something that Bubble could improve. Avoid encoding API Connector JSON box (when there’s no placeholder)
1 Like
Jici
Okay, I'll test it.
Thank you very much.
You have selected RAW as body and not JSON. Switch to JSON or use _*_placeholder_*_ instead of < >
One important detail: Before testing, I successfully initiated the call with fixed values.
It’s not important.
The call is initialized in API connector. But the value you are providing dynamically in the JSON Box could break the payload. Bubble, sadly, encode the entire JSON box (but not in API connector). To avoid issue,you need to set the placeholder in API connector OR use the JSON as a string.
Instead of:
{
"name": "John",
"age": 30,
"car": null
}
That will not work, you can use {"name":"John", "age":30, "car":null} That will work because new line and space will not be encoded.
But best is to set placeholder if you can in API connector
I also found that in your screenshot ,some double quotes are missing. Add them or use :formatted as json-safe to automatically encode string as it should
use services like beeceptor to test your payload.
Hi Jici
I don't know what else to do.
That didn't work. Could you check if the screenshots are correct, and if there's anything wrong, could you give an example?
Look correct but try to send the request to beeceptor and inspect the payload. Also, be sure the header for content-type is ok. There’s api that are case sensitive (For example: Content-type instead of content-type)
1 Like
Hi Jici
Attached is a TXT file with the current JSON.
Please give me an example of how to write it.
(Attachment JSON atual.txt is missing)
Please give me an example of how to write it.
Jici
Please, it still doesn't work.
Can you give a two-line example of how to write to JSON? I'm about to explode.
Aren't those the markers you mentioned?
Please provide two lines of JSON. One string and one number.
What's wrong?
See the screenshots.
Hello,
Did you see my screenshot? It still didn't work. I've tried several ways. I've been at it for 4 days and a simple field that needs to be passed through a connection is being rejected.
This happens because of a line break problem in the value. So if I use JSON-safe to protect the page break, it's enclosed in quotes; otherwise, it breaks the line.
What should I do? Can you help me? My client is waiting, but technically I don't know what to do.
Thank you
Why did you replace by {{ ? This was set correctly with < > .
Yes json-safe is made for dynamic value to encode the string correctly.
If for example "description" have the issue for the format, you should have it in your API connector as
"description":<description>
And in description field box, you will set the value dynamically and use :formatted as json-safe (Current cell’s value:formatted as json-safe). Bubble will encode the string and also add doubles quotes around it
Jici
Answer: I replaced it as another attempt I saw on Google, because it’s also a valid JSON marker. When you use {{, the list of parameters below the JSON text isn’t created in the Bubble API connector, and the workflow allows you to insert the expression directly and doesn’t display a default form. But nothing worked, it’s returning the same error. I’ve tried everything, including with the help of AI.
I tried every possible way for dynamic parameters. The call only works with fixed values in the JSON; the call always starts successfully.
Following step by step, we can see the processes in the workflow working correctly, but when the call is executed, Bubble must be passing the incorrect Customer value to the Asaas company.
Please don’t close the ticket; I need to resolve this. I opened a support ticket with Asaas for them to identify what’s arriving there and respond to the 400 error.
Thank you
The issue is not on Asaas but in your request.
Please share the API connector settings with < > (this is what you should use) and your settings after in dynamic values.
Hi Jici
Well, it’s because you’re picking up the case now, but it was like this before and it was working in production.
You saw a modified test version, but I’ve already tried all the options. I’ll send them all to you.
Following step by step, the value remains intact until the last step of the workflow, I’ll present it to Bubble again.
I used <> with and without quotes, trimmed with safe JSON, only with trimmed, only safe JSON, and together.
Please wait while I send the screenshots, I’ve been without a real solution for 4 days already.
Thank you. Regards
You didn’t applied what I said about encoding your parameters with json-safe.
For example, remove doubles quotes in API connector around and in the dynamic value box, use :formatted as json-safe.
You can do that for all string (with doubles quotes around placeholder) to be sure nothing break the json.
Please do that and share the screenshot after.