Read only API vs the other API what exactly is the difference?
A read-only API token allows other apps to see your Wanikani data, but not make changes to it.
3 Likes
Gotcha so if I used the not read only with Bunpro then the Bunpro would make changes to my Wanikani to reflect words I learned on Bunpro but not on Wanikani yet correct?
This page explains what Bunpro can do with the Wanikani API. It looks like it makes it so you don’t need to do reviews for the same vocab item in both apps, but it says right in step 5 that they don’t modify any data, so it only uses read-only features.
3 Likes
If the app is trustworthy and they ask for a read-only API key, my expectation would be that it would only attempt to use read-only features, and thus the kind you provide wouldn’t actually matter, though it would still of course be good practice to use a read-only key in the situation
3 Likes
No, it won’t. Bunpro only want read access to the kanji you know to update its furigana and known vocab logic. Using a read-only token is just a security measure since Bunpro does not want or need write access.
For instance imagine if Bunpro’s database gets pirated somehow and the various tokens are made public, some troll could use a read-write token to mess up your reviews. With a read-only token they could only get to see your progress and not make any changes.
2 Likes
Read-only is a ticket that allows the holder to peer in the windows of your house and look at your furniture.
Read-write is a ticket that allows the holder to enter your house and rearrange the furniture.
When you give tickets out, you decide who you trust and what you want them to do with the trust you give them. You don’t give a read-write ticket unless BOTH (a) you want your furniture rearranged and (b) you think the person who you give the ticket to will rearrange it the way you want (and not steal it all or set it on fire).
1 Like