Future Hackathon API's

Inspiration

Working on systems / problems / platforms that are not very much integrated with external systems requires lot of coordination among participants and cumbersome transfer of data between the systems. Especially, in the given context, ( for users who participate in multiple hackathons or seasoned hackers), some examples are things like finding new team members, messaging prospective team members, bringing them under one platform, tracking notifications & office hours, setting up everything, etc. I have participated in about 10 hackathons in devpost and other platforms. I found that notifying the project requirements / deliverables (from ideation to submission) , team-building, adhering to rules / updated rules, communication with participants ( using slack, discord , etc ) could have been done much smoother and seamless.
While submitting our solution , we use Google docs, Figma, Github, Discord etc., I believe we can integrate their API's with devpost for simple use-cases for seamless workflow experience so that users can actually spend more time on problem solving rather than organising stuff / peripheral issues.

I was inspired by: JIRA -( API integration with Github, slack, etc) AWS API Gateway for external systems integration. UPI payment gateway ( Used in India for seamless payment processing)

What it does

Exposing Devpost's User , Hackathons , Participants, Skills , Interests API's to external world can help developers , product managers come up with innovative solutions & marketplaces to build teams faster, better notifications, collaborate and manage projects easily.

How we built it

I have wrote down all my previous hackathon experiences (from starting registration to project submission) and identified the repetitive, boring, things prone to errors and pain points , and came up with ideas / actionable items which can add value to the participants , organisers and stakeholders in real-time.

Challenges we ran into

While my solution can help the participants save time and provide seamless experience , I identified that some people may misuse the API's; Limiting the API usage is a possible solution.

Accomplishments that we're proud of

I discussed the idea with other developers and participants and they all liked it and volunteered to build a minimum viable product for demonstration. The whole idea of exposing Devpost API's for developers to build teams and show results fast & validate faster is liked by all.