@Nigel - We’ll look into it and get back to you soon. In the meantime, could you share the context for your requirement – what you’re trying to achieve exactly on this page, so we can provide a better solution?
this is the array of strings that i want to display from browser session .

here is how i had been trying to display it Home
@alitanwir nother issue is i want to save the result of an API response in currently logged in user . Its not saving but its being captured well in browser session . Help with this part as well . here is a screencast Home
@Nigel - Okay, I’ll get it checked and get back to you.
Also, regarding rendering of the response array data, do you want to display it as non-persistent data, or persist it in the collection item and then render the list items in a DataTable?
Thank you for quick update . Yeah the issue of tables you just highlighted is something that i wanted to share with you after the issue of saving a processed result to a current logged user is resolved . I wanted to say from weekend mapping a result on data table has been giving external api failed to load the result , after having a 200 success response like what just happened as i was implementing what you suggested for array . I have other 4 tables that i getting loading issues . Home
Thank you . Patiently waiting !
Hi @Nigel - We need some time to look into it because of the priority tasks in the pipeline. Please expect an update next week. I’ll let you know as soon as we have an update.
If GET calls to the ERC20 endpoint work but the POST contract deployment returns nothing, I’d check whether the request body is being serialized correctly before it leaves the builder — parameters appearing in Postman but not in the app often points to a content-type or body-format mismatch rather than the endpoint itself. Since you mentioned other projects’ external APIs still work, comparing the working config against this one may reveal a difference. Worth regenerating that test key once debugging wraps up.
Thank you .This issue was solved with the help of @alitanwir and would like to appreciate him . Right now am left with these two features which he promised to fullfill this week
- after getting success result on 4 on my external data tables ( 4 tables only , no all are experiencing this problem ) am receiving 404 error data load issue
2 )Then saving a external api issue on currently logged in user after processing
Other issues pending is : i cant create a derived filled and am also having problem with count filters not taking effect . Once these remaining issues are fixed , am set to get into production @alitanwir
The chain and token addresses being on ETH testnet matter here, since Tatum endpoints are network-specific and a mainnet-style param can fail quietly. Worth confirming whether the Post add-on is still sending the same body shape as last week, especially for the multi-token deploy call, which likely needs contract params nested as JSON rather than flat fields. Also check if the exposed key still has the right scope after regenerating it. Comparing the working Postman body against the configured external API field mappings line by line should narrow it down.