Some of the API returns HTTP 403: Authenticated failed
Categories
- 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
Some of the API returns HTTP 403: Authenticated failed
dderek970
Member ✭
Hi! I am a student developer with a great interest in developing a educational dictionary based on od-api. However, I found that some of the APIs returns HTTP 403: Authenticated failed even if I add the app_id and app_key in the request. This situation only happened in some of the APIs like /search/{source_lang}. I've tried both in the live documentation and on my local machine using Python code. It is really frustrating. I just don't know how to solve this, or is there anything I missed? Please help me!
Best Answer
-
TaisFukushima
Member, Administrator, Moderator admin
Hello @dderek970
Prototype account has access only to our API basic functionalities- Entries and Lemmas endpoints and 1000 requests per month.
Developer account gives you access to all data and functionality.
And if you are looking for a bespoken pricing based on requirements, caching and offline usage we would recommend an Enterprise plan.
They are different, please visit this page to check the plans available.
Answers
Hello @dderek970
This error has occurred because there are requests to translations, sentences, search or thesaurus endpoints, which are restricted to users with a Prototype Plan, this means that you will have access only for Lemmas and Entries.
Hi @TaisFukushima, thanks for your attention!
I checked the plan of my application, and it is exactly the Prototype plan.
As far as I know, there are only 4 types of plans(prototype, developer, enterprise and research) and these plans have no differences other than the frequency of API usage. Am I right about this?
Looking forward to your reply!