I am making a POST request from Bubble to a third-party text-to-3D service. When I initialize the call, the returned ID value is rounded. When I set up the same POST request in other app-building tools, the returned ID value was not rounded. The error seems to be on the client side, i.e., Bubble is causing the issue.
Has anyone run into a similar issue?
Here you can see the “id” specified in the GET request and the returned “id” value that is rounded:
The issue I am encountering is in the response the API call provides. The error seems to be occurring on the client side when the POST response is returned. I.e. there isn’t a data type to define, as this is the raw JSON response from the server.
Here is another example where Bubble is rebounding the Returned ID value. I believe this is a BigInt problem, but I’m hoping someone may have a suggestion for a quick fix.
I did a few test with requestbin and didn’t get this issue. For me, it sound strange that, if really Bubble round it, you don’t get an error from API with a wrong ID… Can you share more the end of url in API connector (with the [ ] part and what you have before)?