Heyhack API

Name: Heyhack API
Brand: Heyhack API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationapiKey3 EndpointsREST

For Agents

List existing hackathons, create new ones, and register teams via API key authentication for the Heyhack hackathon-management platform.

Install Jentic One Beta

Connect the Heyhack API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Heyhack API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Heyhack API.

List all hackathons currently visible to the authenticated organiser

Create a new hackathon record on Heyhack with title, dates, and metadata

GET STARTED

Start building with Heyhack API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Heyhack API for, with concrete tasks.

★ Community Event Listing

Developer communities and university programs use GET /hackathons to power a 'live hackathons' page on their site, polled hourly to reflect new events without manual updates. The same call can drive a Slack or Discord bot that announces new hackathons as they're created in Heyhack.

Call GET /hackathons, filter for events with start_date in the next 30 days, and post the titles to a Slack channel.

Programmatic Team Registration

Organisers bypass the standard signup form by sending team details directly to POST /teams from a custom landing page or partner platform. This lets organisers integrate hackathon registration into existing community signup flows while Heyhack still owns team data and event coordination.

Submit POST /teams with name 'Quantum Otters', members array, and hackathon_id 1234, then confirm the team appears in GET /hackathons output.

Programmatic Hackathon Provisioning

Sponsors running multiple events provision hackathon records via POST /hackathons from an internal admin tool, attaching dates, sponsor logos, and prize details. This avoids manual setup in the Heyhack UI when launching dozens of regional or themed events at once.

Call POST /hackathons with title 'Climate Tech Sprint', start_date and end_date, and a sponsor list, then verify the new hackathon id is returned.

AI Agent Event Coordination

Through Jentic, an AI assistant can answer 'what hackathons are running this month?' by calling GET /hackathons or register a team on a user's behalf. Jentic's vault holds the API key, so the agent never sees the credential while still completing multi-step coordination.

Search Jentic for 'list hackathons', execute GET /hackathons, and summarise the upcoming events in plain language.

Key Endpoints

3 endpoints — the heyhack api offers a focused interface for hackathon and event management.

METHOD

PATH

DESCRIPTION

GET

/hackathons

List all hackathons

POST

/hackathons

Create a new hackathon

POST

/teams

GET

/hackathons

List all hackathons

POST

/hackathons

Create a new hackathon

POST

/teams

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Heyhack API keys are stored encrypted in the Jentic vault. Agents call Heyhack via Jentic and the Authorization header is injected per call, so the raw key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list hackathons' or 'register a team') and Jentic returns the matching Heyhack operation with its input schema, so the agent calls the right endpoint without scanning the spec.

Time to first call

Direct Heyhack integration: a few hours for auth setup and JSON parsing. Through Jentic: minutes — search, load schema, execute.

FAQs

Specific to using Heyhack API through Jentic.

What authentication does the Heyhack API use?

Heyhack uses an API key passed as a token in the Authorization header. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the agent never holds the raw value.

Can I register a team for a hackathon with the Heyhack API?

Yes. POST /teams accepts the team name, members, and target hackathon_id. The same call can be wired to a custom signup form so registrations flow into Heyhack without using the default UI.

How many endpoints does the Heyhack API expose?

The current spec covers three endpoints: GET /hackathons, POST /hackathons, and POST /teams. The surface is intentionally narrow and focused on listing events and onboarding teams.

How do I list hackathons through Jentic?

Run pip install jentic, search for 'list hackathons', and execute against GET /hackathons. Jentic resolves the API key from the vault and returns the JSON response so the agent can filter or summarise the events.

Does the Heyhack API support webhooks for new registrations?

Webhook delivery is not exposed in the current spec; new team registrations are observed by polling GET /hackathons or by relying on Heyhack's UI-side notifications. For real-time mirroring, schedule a periodic GET and diff the team list.

Heyhack API

Connect the Heyhack API to your agent

Capabilities

Start building with Heyhack API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs