API
API overview
The HackathonRadar REST API for hackathons, organizers, sponsors, stats, inbound lead enrichment, suppression and saved views
The HackathonRadar REST API gives your own tools the data you see in the product: hackathons from 40+ platforms, their organizers and sponsors, market stats, and endpoints that enrich inbound sponsorship leads. Every request needs an API key from an Enterprise account.
Base URL and access
| Base URL | https://www.hackathonradar.com |
| Authentication | Authorization: Bearer <your key> on every request |
| Plan | Enterprise. Create keys at /settings/api-access |
| Format | JSON, except exports, which return CSV |
Always call the www host. Requests to the bare domain are redirected, and most HTTP clients drop the Authorization header when they follow that redirect, so the request fails with 401.
Quickstart
Create a key at /settings/api-access, then fetch one hackathon. The id is the UUID or the slug at the end of a hackathon page URL (/database/hackathon/<slug>).
curl https://www.hackathonradar.com/api/hackathons/HACKATHON_ID \
-H "Authorization: Bearer YOUR_API_KEY"A 200 returns the hackathon with its sponsors, organizers and quality score. A 401 means the key is missing or wrong.
Endpoint families
| Family | Endpoints | Page |
|---|---|---|
| Hackathons and stats | /api/hackathons/{id}, /api/hackathons/export, /api/stats/* | Hackathons and stats |
| Organizers and sponsors | /api/organizers, /api/sponsors, their {id} and export routes | Organizers and sponsors |
| Inbound enrichment | /api/v1/inbound/* | Inbound enrichment and suppression |
| Suppression | /api/v1/suppression/check, /api/v1/suppression/add | Inbound enrichment and suppression |
| Saved views | /api/v1/saved-views | Saved views and reports |
The machine-readable contract is the OpenAPI file at /openapi.yaml. The full API reference renders it with every schema. To receive new hackathons as they are listed instead of polling, use webhooks.