Hello. Please add very simple title search.
Get rid of this completely uninformative error “ERROR: you can’t get there from here!” and make it more obvious in your documentation what parameters are mandatory and what are optional. Make your documentation more informative overall.
And please, for the love of everything nice in this world, use goddamn associative arrays.
Thank you.
הצטרף לדיון - הוסף תגובה למטה:
its going to be a while as there are a lot of other people who need to change their apps… feel free to use api.new as this will just become a symlink once things get migrated to api.cgi
Yes, great. Now just waiting for you to push it to live (api.cgi) so that I can change it for my client.
You have inspired me to pull my finger out…
try this: replace apic.cgi with api.test in your query.
You can now do a simple query by just specifying a q=<value> and all results should be in associative arrays.
Let me know how you get on.
Great. Thanks. Best of luck
Apologies what I showed you was for the nfinfo array in the title return.
In your example, you are correct 0,4 are the netflix id (legacy issue) basically here is the breakdown:
[0] => Array
as for your other requests they will be taken under advisement.
Here:
Some items don’t seem to match. And 0 and 4 seem to be the same.
Also, by simple search, I meant just one parameter, without 1 million other ones. Like, why not make them default by the processor if they’re not there instead of expecting user to pass them with every request
As I said previously, I agree that associative arrays are clearer and we will be going that direction in the future… This api was originally adapted directly from the back end used by the uNoGS website, so it isn’t very user friendly at the moment.
In regard to the q parameter… Please use the following template to do a search…
https://unogs-unogs-v1.p.mashape.com/api.cgi?q={query}-!{syear},{eyear}-!{snfrate},{enfrate}-!{simdbrate},{eimdbrate}-!{genreid}-!{vtype}-!{audio}-!{subtitle}-!{imdbvotes}-!{downloadable}&t=ns&cl={clist}&st=adv&ob={sortby}&p={page}&sa={andor}
All the parameters are specified in the DOCS. If you are unsure as to the fields in the returned array please see the following which is also in the announcement section:
“nfinfo”: [
What other fields blank. It’s not even explained anywhere. If you just have q parameter, you get that error I’ve mentioned.
Also, associative arrays are not just easier for new users, it’s also simply more reliable. If for any reason order of elements in the response is changed, it might mess up things.
apologies that you are getting so frustrated… I agree that associative arrays would be a lot easier for a new user and it is something we are looking into on a new version of the API. In regards to a simple title search, you can search by title by just leaving the other options blank.