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
Hi team, I'm working on a academic research on crowdsourcing and is using your public api to gather some data. Previously I opened an issue regarding the registrant list (#367 ) and really appreciate your timely response!
I got a new question regarding the score of winner for Completed challenges. In the V5 Challenge API there is no point field in the winner array. I find the issue #71 called this out and it was replied "fixed". However in the current Challenge api there is still no point field from, for example, https://api.topcoder.com/v5/challenges/?status=Completed&perPage=1
Is there a way I can access winner's submission score with the authorization level of Community member?
If not, is there a way I can apply for higher level access supported with document from my college which prove my purpose for using the Topcoder's data for academic research?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi team, I'm working on a academic research on crowdsourcing and is using your public api to gather some data. Previously I opened an issue regarding the registrant list (#367 ) and really appreciate your timely response!
I got a new question regarding the score of winner for Completed challenges. In the V5 Challenge API there is no
point
field in thewinner
array. I find the issue #71 called this out and it was replied "fixed". However in the current Challenge api there is still nopoint
field from, for example, https://api.topcoder.com/v5/challenges/?status=Completed&perPage=1Is there a way I can access winner's submission score with the authorization level of Community member?
If not, is there a way I can apply for higher level access supported with document from my college which prove my purpose for using the Topcoder's data for academic research?
Thanks!
The text was updated successfully, but these errors were encountered: