Entries API endpoint return not correct pronunciation for some words as RECORD, IMPACT...
Categories
- 329 All Categories
- 3 Language datasets
- 9 News and updates
- 21 API endpoints
- 15 Review my code
- 6 Tutorials and presentations
- 92 Frequently asked questions
- 5 How to get useful technical help
- 2 Member guidelines
- 12 Suggest an improvement
- 58 Report a bug
- 10 Ask the Community: Other
- 56 Ask the Community: Technical and operational questions
- 62 General
Entries API endpoint return not correct pronunciation for some words as RECORD, IMPACT...

I have tried on record and impact. The results can return 2 forms: noun and verb but the pronunciation of verb form is not correct
exp:
"language": "en-us",
"lexicalCategory": {
"id": "verb",
"text": "Verb"
},
"pronunciations": [
{
"dialects": [
"American English"
],
"phoneticNotation": "respell",
"phoneticSpelling": "ˈrekərd"
},
{
"audioFile": "https://audio.oxforddictionaries.com/en/mp3/record_us_1.mp3",
"dialects": [
"American English"
],
"phoneticNotation": "IPA",
"phoneticSpelling": "ˈrɛkərd"
}
],
"text": "record"
I have expected the verb form should be returned as the result in
https://www.oxfordlearnersdictionaries.com/definition/english/record_2
Is there any way for me to get the correct expected result of pronunciation in this case for other similar words?
Thanks
Comments
Hi @elgroupwork
Apologies for the late reply - and thanks for flagging this up to us.
Let me forward this to the right colleagues, and I'll get back to you as soon as I hear back from them.
Hi @Simone,
Thanks for your response. I am looking forward to hearing any update from you
Hi @elgroupwork,
Sorry for the late reply, I was double-checking things with my colleagues.
This is actually an issue they were already looking into – but thank you very much indeed for flagging it up!
It has now been fixed, and it should be deployed with an API update due to be released soon.
You will be able to then get the correct pronunciation to each of the parts-of-speech of the verbs you mentioned:
I hope this is helpful but do let us know if there is anything that is not quite right!
Hi @Simone,
Thank you for your update and information on audio for other forms of "record"
BTW, in my opinion, I think this could be a generic issue that could happen to other words that have 2 forms of pronunciation not only the case of "record", and we haven't had change to reach to them. So it should be a generic fix not only for "record"
I will test again on the swagger and with my api key latter.
Thanks
Hi @elgroupwork
Yes, absolutely - as I said this was already being looked at by my colleagues and should be fixed now, but do flag up if you notice anything that is still not correct!
Hi @Simone
Thank you for your team effort on the api. I have tested some words with my API key and the response returned correct results. I think we could close this thread because it was fixed properly.
Thanks for your continued feedback, @elgroupwork - I've closed the thread, but if you encounter any other problems, please get in touch, or post a new thread.
Good luck with your project!
(Incidentally, we are always happy and curious to hear about what our users are building with the API - so please feel free to get in touch to let me know more about your project (you can message me privately if you prefer).