You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just realized that the package just can't do multi-word lookup like "break the law" or "under the weather". I couldn't figure out how to make it work for xml endpoint, so this works:
GET https://www.dictionaryapi.com/api/v3/references/thesaurus/json/break%20the%20law?key=MYKEY
but the similar request to the XML endpoint, doesn't:
GET https://www.dictionaryapi.com/api/v1/references/thesaurus/xml/break%20the%20law?key=MYKEY
I guess this is yet another reason to finally switch to JSON API - which, sadly, would require a big overhaul.
Reminder, initially I wrote the package when JSON version of the API did not exist yet. I guess, Webster still keeps xml version for backward compatibility. A potential downside of switching to JSON that it's a rate-limited endpoint, the FAQ says it's limited to 1K queries a day. Whereas xml endpoint doesn't seem to enforce that limit.
The text was updated successfully, but these errors were encountered:
I just realized that the package just can't do multi-word lookup like "break the law" or "under the weather". I couldn't figure out how to make it work for xml endpoint, so this works:
but the similar request to the XML endpoint, doesn't:
I guess this is yet another reason to finally switch to JSON API - which, sadly, would require a big overhaul.
Reminder, initially I wrote the package when JSON version of the API did not exist yet. I guess, Webster still keeps xml version for backward compatibility. A potential downside of switching to JSON that it's a rate-limited endpoint, the FAQ says it's limited to 1K queries a day. Whereas xml endpoint doesn't seem to enforce that limit.
The text was updated successfully, but these errors were encountered: