contest-hive / contest-hive

All Contests in One Place. No more keeping track of future contests manually! Contest Hive is all you need.

Contest Hive - Contests at Your Fingertips

Live at contest-hive.vercel.app

Table of Contents

• Table of Contents
• Why Contest Hive?
• Features
• Platforms
• API
  • API Endpoints
  • API Response Format
• How Does It Work?
• Contributing
• License
• Links

Why Contest Hive?

Contest Hive saves your time by providing you all the upcoming contests from various platforms. So you don't have to visit each platform to check for upcoming contests.

All contests in one place. Isn't it cool?

If you want to know how this is different from StopStalk, then you can read the About Page of Contest Hive. It explains the differences between Contest Hive, StopStalk and Kontests.

Features

• Upcoming contests from 7 platforms
• Filter contests by start time or platform
• Contests Update Every 5 Minutes
• Google Calendar Integration
• API for developers
• No Rate Limit on API
• Fully Responsive Design
• Dark Theme to save your eyes 👀

Platforms

• Atcoder
• Codechef
• Codeforces includes Codeforces GYM
• Hackerearth
• Hackerrank
• Leetcode
• Toph

API

Contest Hive provides an API for developers to fetch upcoming contests. The Documentation for the API can be found here.

The documentation fully explains how to use the API and the response formats.

API Endpoints

Endpoint	Alias	Description
/api/		Root Endpoint of api
/atcoder	/1	Returns all the future contests information from AtCoder
/codechef	/2	Returns all the future contests information from Codechef
/codeforces	/3	Returns all the future contests information from Codeforces
/hackerearth	/4	Returns all the future contests information from Hackerearth
/hackerrank	/5	Returns all the future contests information from Hackerrank
/leetcode	/6	Returns all the future contests information from Leetcode
/toph	/7	Returns all the future contests information from Toph
/codeforces-gym	/8	Returns all the future contests information from Codeforces GYM

API Response Format

The API returns a JSON object with the following format for each platform:

{
  "ok": true,
  "data": [
    {
      "title": "UNIQUE VISION Programming Contest 2023 Autumn(AtCoder Beginner Contest 323)",
      "url": "https://atcoder.jp/contests/abc323",
      "startTime": "2023-10-07T12:00:00Z",
      "endTime": "2023-10-07T13:40:00Z",
      "duration": 6000,
      "platform": "Atcoder"
    },
    {
      "title": "AtCoder Regular Contest 166",
      "url": "https://atcoder.jp/contests/arc166",
      "startTime": "2023-10-08T12:00:00Z",
      "endTime": "2023-10-08T14:00:00Z",
      "duration": 7200,
      "platform": "Atcoder"
    }
  ],
  "lastUpdated": "2023-09-26T14:31:22Z"
}

The response types and details are explained in the API Documentation.

How Does It Work?

Contest Hive uses Github Actions to run a python script every 5 minutes which fetches the contests info and stores them in a JSON file. The JSON file is then used and cached by the Contest Hive API to serve the data to the users.

This way, the API doesn't have to fetch the data from the platforms every time a user makes a request.

The Backend repository of Contest Hive can be found here

Contributing

Contributions are always welcome! Feel free to raise a PR. If you have any suggestions or want to report a bug, please open an issue.

License

Contest Hive is licensed under the Apache License

Links

• Contest Hive - Home Page of Contest Hive
• Contest Hive API - API Endpoint of Contest Hive
• Contest Hive API Documentation - Documentation of Contest Hive API
• About Page of Contest Hive - About Page of Contest Hive
• Credits Page of Contest Hive - Credits Page of Contest Hive

contest-hive's Issues

Leet code contests' information not getting updated

The scrapper is failing to parse leetcode contests.