掲示板 Forums - Interested in working with a renshuu API?

edict_ent added

a number of config tags added - I'll get a def list out later

usage notes are hidden for now, will decide later if/when to display them.

unique-furigana, common-hiragana are a few. Some others from jmdict (a subset).

Do you mind trying now? If it still doesn't work, please pass me the curl command so I can drop your key in and replicate it on my end.

Removing the last term from a list using the api causes some issues. I've got a private list called "empty list" that I put a single term in, then removed it with the api. I can no longer see it in api requests, nor in the dictionary "plus button". However, I can see it in my list of lists, and trying to edit it causes an error to show up.

It seems that the dictionary will warn you if you try to remove the last term from a list, asking for confirmation that you want to delete the list.

Actually, I made a mistake. It turns out that the list does show up in the api requests. I think it showed up in a different order so it didn't show up in the same place and I thought it was missing.

As for how to solve the issue, maybe just support empty lists from the community list page. It seems that only the pencil button throws an error here:

Everything else seems to work fine (viewing contents, study button, add to schedule, and delete).

When using the put/delete, the word object should now have either a "result" or "error" field describing what happened.

And, I think you already noted this, but it doesn't need the force (and doesn't delete the lists either - that code was in there, but it's been taken out.)

While I continue to work on the term interface, I'd like to jump into schedules next. Repasting what was mentioned earlier:

GET /v1/schedules
{
    "user": "abc",
    "schedules": [
        {
            "name": "Genki 1 Words",
            "review": 123,
            "learn": 123
        },
        ...
    ]
}

Here's everything I can think of that you may need for any schedule

name

id

term stats (# of terms, hidden, studied, not yet studied, cannot study)

review/learn for the day

# learned for today, this week

current pace settings

Anything else?

Don't have all the info, but the basics are in there

GET /v1/schedule

GET /v1/schedule/:id

enjoy!

You can get your API key if you go to the experimental section of the settings.

Hi everyone,

I've written a chrome extension that uses the new renshuu apis. It is open sourced here: https://github.com/buruburukun/renshuu_helper You can use it to search for terms on any website and add them into lists and schedules. Please give it a try. It is not published to the chrome web store yet as things are still unstable. There are installation instructions in the readme. If you have any issues or suggestions please let me know.

The following is for Michael.

Questions:

1. What is the meaning of this in search results?

"config": { "3": "ent_primary" }

What are all the possible values? For example, I've also seen

"1": "unique-furigana"

Bugs:

1. Inconsistent dictionary results?

Searching for 入賞 using the api (note that there are 2 definitions in the list):

"def": [ "winning a prize, placing (high", "in a contest)" ]

Searching on renshuu (note the semicolon):

winning a prize, placing (high; in a contest)

2. You can attempt to PUT/DELETE a word from a schedule that does not exist (perhaps it is someone else's schedule?), and the request succeeds (200) with no result/error field. I hope this wouldn't edit someone else's schedule.

3. For GET /v1/word/:id requests, the returned total_pg always seems to be 0. I did some calculations to determine the maximum page.

4. For GET /v1/word/:id requests, if the requested page is greater beyond the last page, the returned page will be the last page, and the returned "pg" will be 0. Similarly, if the requested page is negative, the first page will be returned and "pg" will also be 0.

Feature requests:

1. Can we get the word ids for the alternate forms? I believe these can be added into lists/schedules, but searches only have the id of the main entries.

2. Can we streamline getting the api key into the extension? I've got right click on renshuu -> populate the api key in the extension, but it involves opening the settings panel to get the appropriate element loaded (and some imprecise selectors). I think the easiest would be a hidden element that is always present that can be referred to by id. Or if someone else has good suggestions for how to do this...