You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to use Leetcode APIs to build an automated system for Weekly contests where if people solve certain questions they earn CodeyCoins.
This is a research task to figure out if Leetcode API has the features we need to actually build this, or if we need any separate third party API for this data.
The data we get from the user:
leetcode username/ profile url
The data we want to access:
Attempts on a particular question (Date + Time for the latest)
If they have solved the question (Date + Time for the latest)
Which language they solved the question in (optional)
Their solution speed and memory usage data (just take the latest) (optional)
I tested it on Postman. The query returns info on all past contests, but we can always filter out to grab the Weekly Contests ones. It doesn't give us info on specific questions, so my suggestion is that we can just simply reward CodeyCoin based on the number of questions they solved. Unfortunately, it doesn't give us info for the optional criteria you listed, but other than that, everything else looks promising.
Unfortunately again, I myself have never attempted a Weekly Contest (never really got the time) so it would be nice if you or someone else, who have attempted a Weekly Contest, to test out the query and check out the data. But I'm pretty confident about the query already.
We want to use Leetcode APIs to build an automated system for Weekly contests where if people solve certain questions they earn CodeyCoins.
This is a research task to figure out if Leetcode API has the features we need to actually build this, or if we need any separate third party API for this data.
The data we get from the user:
The data we want to access:
Currently we are using the leetcode api here https://github.com/uwcsc/codeybot/blob/main/src/components/leetcode.ts
The text was updated successfully, but these errors were encountered: