...
| Pros | Cons | |
|---|---|---|
| no impact on existing api's | need to manage one more endpoint | Reduce testing effort |
| All changes regarding public access will be handle separately Required to make public api secure. Based on this we can't configure some rate limit | ||
Proposed Solution 3:
We can Implement Captcha for public api, if captcha is valid then only api call will be process.
Example: In case of page api. By default user can make page assemble call and default response system can Catch it for some TTL. So if user is again making same call (means without passing any filters or with default filters only) then catch response will be served. Now user can select different filters and then call apply button , then we can ask user to verify Captcha and once captcha is verified then only call will trigger.
OR, For public user we can asked Captcha verification first once Captcha is Verified , internally it will create user session for Particular time and then user can do all activity.
Problem Statement 2:
Proposed Solution 1:
...