- 276 All Categories
- 4 LexiStats Corner
- 12 Review my code
- 6 Tutorials and presentations
- 89 Frequently asked questions
- 5 How to get useful technical help
- 2 Member guidelines
- 12 Suggest an improvement
- 56 Report a bug
- 7 Ask the Community: Other
- 52 Ask the Community: Technical and operational questions
- 57 General
We’re thrilled to tell you about the exciting new features we’ve added to the Oxford Dictionaries API!
With the release of V2.2, you will now have access to an assortment of new tools and languages to improve your experience.
If you hold a Developer or Enterprise account, our new Words endpoint will allow you to swiftly retrieve all the information you need. You’ll receive definitions, pronunciations, example sentences, grammatical information, and word origins in one neat package.
We know you’ll enjoy using this new feature and are looking forward to seeing what you do with it.
Additionally, all accounts will benefit from access to our bilingual dataset for Italian-English and English-Italian, and two Nigerian languages: English-Igbo, and English-Yoruba.
If that’s not enough, we’ve updated our English monolingual dataset, too.
You can also explore our new data feature that provides one or more encodings of a distinct tonal variation for a lexical item or its translation. And we have made improvements to our thesaurus endpoint to support grammatical features, while our search endpoint now has increased accuracy and reliability.
All this alongside general bug fixes and performance improvements will enhance your Oxford Dictionaries API experience.
You can find more information about these updates on our Updates and Release Notes page on the API portal.
If you have any comments, questions, or feedback about these updates, let us know in the comments below (but if you have a very specific question, you might want to start a new forum discussion).
I've noticed that v2 offers lesser examples at Sense level. Please compare v2 Sense data of following words with v1:
First off, I've found V2 of the API to be leaps and bounds better. Congratulations on the launch!
I also find the content of the new API docs to be very thorough and useful.
However, one little thing that would make it much more readable is to, instead of writing something like:
PronunciationsList [ Inline Model 1 ]
Just inline the model so that I don't have to scroll down to find out what the values are:
PronunciationsList [ audioFile (string, optional): The URL of the sound file , dialects (arrayofstrings, optional): A local or regional variation where the pronunciation occurs, e.g. 'British English' , phoneticNotation (string, optional): The alphabetic system used to display the phonetic spelling , phoneticSpelling (string, optional): Phonetic spelling is the representation of vocal sounds which express pronunciations of words. It is a system of spelling in which each letter represents invariably the same spoken sound , regions (regionsList, optional): A particular area in which the pronunciation occurs, e.g. 'Great Britain' ]
I don't really see the advantage of having this extra layer of indirection.
Hope this feedback is useful!