Frequently asked questions
Frequently asked questions
- How can I sign up for the API?
- How can I log in?
- Where can I find information about the different plan options?
- How much does the API cost?
- How much will I be charged and when?
- How can I change my plan?
- Are there any monthly limits?
- How can I start integrating this data into my project?
- How can I delete my account?
The Oxford Dictionaries API v2 has flexible plans to suit all types of application. You can register for a Prototype account for free. Once registered you can get started using the data straight away with your unique App ID and App Key. If you want to explore the API before registering our live documentation offers a playground to try real requests and view the data. For the full features and capabilities of the API you will need to register here.
You can log in to your account by clicking the 'sign in' option from the main menu. If you have not already created an account, please select a plan that suits you and create an account.
You can view our plans here. We offer flexible plans to suit all types of application, based on the functionality you require. Any application requesting the ability to cache data will need to get in touch to discuss an Enterprise plan.
We offer flexible plans to suit all types of application, based on the functionality you require. Our developer plan is a pay-as-you-go model which means you only ever pay for what you use, and the more you use, the greater the discount on the cost of each request. You can see more information about our pricing here.
Our pay-as-you-go model means you only ever pay for what you use, and the more you use, the greater the discount on the cost of each request.
Charges are calculated at the beginning of each calendar month for the month previous and charged to your payment card in Great British Pounds (GBP). If you change your Application Plan during the month you are still liable for any charges accrued in that month up to that date. In general, invoices for all paying customers are generated on the first day of the month. They are then issued a few days later, at which point you will be notified of the amount that is due, and then you will be charged another two days later.
You can change your Application Plan at any time using the ‘Update my plan’ button on the Applications page in your account.
If you have a Prototype account you are limited to 60 request per minute and 1,000 requests per month.
Developer plans have an allowance of 500 requests per minute and an unlimited monthly total. If this does not meet your requirements then please fill out our Enterprise form to get in touch and discuss your needs.
Please contact us and we will delete your account for you.
- Who built the Oxford Dictionaries API?
- What can I do with the Oxford Dictionaries API?
- Which dictionary does the API data come from?
- Is this an Oxford English Dictionary API?
The Oxford Dictionaries API was built by a team in Oxford Dictionaries which is a part of Oxford University Press. You can find out more about our API here, and more about Oxford Dictionaries here.
The Oxford Dictionaries API offers an easy way to access powerful lexical data (words, definitions, translations, audio pronunciations, synonyms, antonyms, parts of speech, and more) to use in your apps and websites. Please read our Terms and Conditions before signing up. If you would like to discuss your use of the API then please complete the Enterprise form to contact us.
The Oxford Dictionaries API provides access to our current English dictionaries which are available on en.oxforddictionaries.com. This is our most comprehensive current English dictionary dataset and includes enhanced, updated versions of the Oxford Dictionary of English and the New Oxford American Dictionary. It includes more than 350,000 entries and is regularly updated with new words, senses, and definitions.
We also have content in Spanish, German, Portuguese, Romanian, isiZulu, Northern Sotho, Malay, Indonesian...and many more, and we're adding more all the time. Take a look at our supported languages page for the most up-to-date list.
Oxford Dictionaries and the Oxford English Dictionary both come from the same publisher, Oxford University Press, but are different products. While Oxford Dictionaries reflects current usage of English, the OED records how language has developed over time. You can learn more about the difference between the OED and Oxford Dictionaries here.
- Can I use the API in a commercial project?
- Can I use the Oxford branding in my application?
- Can I cache data?
- Where can I find your terms and conditions?
Use of the Oxford Dictionaries API as a commercial product is permitted in line with our terms and conditions.
Please visit our branding resources page for the guidelines on using our branding and the appropriate logo.
Caching or any saving and use of the data offline is only permitted on a case by case basis - please complete our Enterprise form to request this functionality. Including estimates of how much data you would initially anticipate caching will expedite the consideration process.
Our terms and conditions can be found here.
In the API, we currently offer content in English, Spanish, German, Portuguese, Romanian, isiZulu, Northern Sotho, Latvian, Malay, Indonesian...and many more, and we're adding more all the time. Take a look at our supported languages page for the most up-to-date list.
If you’re looking for a dictionary dataset for a language which isn’t currently available via the API, we might still be able to help. We have over 35 language datasets, from Afrikaans to Vietnamese, available to license via Oxford Dictionaries Licensing.
Please take a look at our supported languages page. If your requested language isn't available through our API, it may be available through our licensing programme. If licensing is not the right option for you, please do let us know, as the more a language is requested, the more likely it is that we will be able to prioritize it for inclusion in the future.
If you explore our documentation page, you will find information on what each error code might mean under the 'response messages' for each endpoint. If you need any further help on resolving your problem, you may find our forum a useful resource for input from other developers using the API.