You need the upc scan, it is part of the Query parameters. Issue is in the API response, not the parameters.
I tested by adding the UPC code in the Query parameters, and as you can see it gave results (This UPC code existed in the DB), but the response is still not properly formatted for Adalo.
If you take a look at the Cocktails API and add “drinks” to the “Results Key” it returns a proper array:
As I mentioned, ADALO cannot handle the 1 Result “JSON Object”.
Hi JL_LJ thanks very much for your insights. I understand what you have explained, but I do have 1 question based on your cocktails API example:
I looked at the rapidAPI for this and wondered how did you determine that the results key was “drinks”?
Thanks @JL_LJ! Awesome!
Hi Gaby,
After thinking this I don’t think you need External collection for this because it only returns the quote and ID only. And you can do this with Custom action.
Here’s a video :
In here I have added a Input to store the return quote and display it. Or you can create a variable in the Users collection and store it there if you have User Profiles. Or you can create another collection and store there and show.
Just for information : Abracadalo also has a Nice Random Quote API : Random API | Abracadalo API Handbook
And a video about that too :
Thank you
Hi @Gaby ,
if you take a look into the Results in Rapid API, you can see the results are grouped under the Results key “drinks”
If you observe Airtable, same principle, but under “records”
Ok @JL_LJ Now I get it - I had to subscribe and run the “test endpoint” to get the “results key”. Thanks for shedding some light on this!
Wow @dilon_perera thanks for taking the time to put this info together. I will review and give feedback.
I had worked around my problem for my current project by using an API that was outside the RapidAPI hub, but I really wanted to understand the possibilities and limitations using RapidAPI for future projects. So I really appreciate your and @JL_LJ feedback. Hopefully @Zwood finds a solution to his immediate challenge based on all these valuable discussions!
