Some love for the API

Posted in

#201 by kurothing
2018-05-12 at 12:46
It appears when you log in via the API, the username must be transformed to lowercase before being sent...

Can this be confirmed? And if so, could we possibly get something server side to do that transformation for us in the API so that issues like this don't occur.
#202 by yorhel
2018-05-12 at 13:10
Ah, that's a bug. I wasn't aware that the web login form accepted uppercase characters in the username, but it does, and obviously the API should be consistent with that.

Fixed.
#203 by kurothing
2018-05-13 at 23:56
On the API Documentation page, it states....

Design overview
TCP-based, all communication between the client and the server is done using one TCP connection. This connection stays alive until it is explicitely closed by either the client or the server.

Does this imply that the connection to Vndb should remain opened for as long as possible, or should it be closed as soon as it's finished being used? Or does it not matter and it's up to developer preference?
#204 by yorhel
2018-05-14 at 04:56
Does this imply that the connection to Vndb should remain opened for as long as possible,
Whatever makes the most sense for your application.
#205 by micah686
2018-06-03 at 19:11
With work being done on a site redesign (Utawarerumono.vndb.org), will that also include any changes/rework of the API at all?
#206 by yorhel
2018-06-03 at 19:16
The API and the site share very little code, so I have nothing planned in that regard at the moment. Do you want a reworked API or were you just asking out of curiosity?
#207 by micah686
2018-06-08 at 23:40
A little bit of both. There are a few sections of the API that may need some work. Also, even though I know you said that the API and the site share very little code, I figured right after a site redesign like what is planned would be a good time as any to rework the API.
#208 by mooncake4132
2018-06-13 at 04:54
It seems like the "instance of" information for the characters is currently unavailable in the APIs. Is there a plan to make that happen?
#209 by yorhel
2018-06-13 at 16:07
@208: Added.
#210 by mooncake4132
2018-06-13 at 16:42
Wow. Thank you. Didn't expect it to be added that quickly.
#211 by hitchiker42
2018-07-21 at 01:23
Would it be possible to add the revision number and/or the timestamp of the last modification as a field/filter? I cache results from api queries, but as it currently stands there is no way to check if the information I have cached is out of date. Currently I just set a limit on my end, but this can easily result in out of data data and unnecessary updates on my end. I'm not sure how many people actually use the api so it might not be an issue, but I imagine adding something like this could reduce server load by reducing the amount of data transferred.

I've looked through the code/database schema and it doesn't seem like it would be too difficult to implement this, though it does present some issues (like how exactly a filter for the revision number would work.) If you have a better way to solve this problem or if there's a way with the current api that I'm just missing that would be fine too.
#212 by micah686
2018-07-27 at 04:30
I would appreciate this as well, since it would help with determining to use cached data, or live data from the API
#213 by rampaa
2018-08-05 at 08:50
It would be great if we could specify (minimum) tag scores when filtering VNs by their tags.
#214 by rampaa
2018-08-06 at 09:41
Is there a way to get child tags of a tag through the API?

Also (released>"2005" and released<"2018") works as intended but (released>"2005-1-1" and released<"2018-1-1") returns nothing. Am I missing something obvious?Last modified on 2018-08-06 at 09:45
#215 by yorhel
2018-08-06 at 11:45
but (released>"2005-1-1" and released<"2018-1-1") returns nothing
It should return an error, according to link - "2005-01-01" ought to work though, format is YYYY-MM-DD.

Reply

You must be logged in to reply to this thread.