---
title: Event Admin API
description: Automate an event over HTTP, covering authentication, the OpenAPI reference, and what the API can do.
sidebar:
  badge: Starter+
---

Each event exposes a full **Admin API** over HTTP: broadly the same operations the event dashboard performs, available to your own scripts and integrations (score trackers, custom dashboards, CI jobs). API access is included on **Starter and above**; you issue and revoke keys from the event's **API keys** page. See [Create API keys](/organizers/how-to/create-api-keys).

## Base URL and authentication

The API is served from your event's own site. Its **base URL** is the **API URL** shown on the API keys page; copy it from there once your event is provisioned.

Authenticate every request by sending your key as a bearer token:

```
Authorization: Bearer <your-api-key>
```

A valid key grants full access to that event's admin operations; there are no per-resource scopes. Treat a key like a password and give each integration its own. Keys are created and revoked from the **API keys** page in the dashboard, not through the API itself.

## The endpoint reference

The authoritative list of endpoints (with their parameters, request bodies, response shapes and code samples) is the [**API reference**](/api), one page per operation, grouped by area. It is generated from the API itself rather than written by hand, so it matches what the endpoints actually accept.

If you'd rather work from the raw document, your event serves its own OpenAPI JSON at **`/api/admin/openapi/json`** (your API URL with `/openapi/json` on the end). It needs no key to read, and it describes that event's running version, useful for generating a client or diffing against the reference.

Prefer a terminal to raw HTTP? The [`athena` CLI](/organizers/how-to/use-the-cli) covers nearly every endpoint below as a command. Its `--url` takes the API URL from the API keys page, with or without the trailing `/api/admin`.

## What the API covers

At a high level, the API spans the same areas as the event dashboard.

Content you can create, update, and delete:

- **Challenges** and **drafts**: author and publish challenges; patch a challenge's own fields, and manage its hints, files, flag and prerequisites one at a time. Lifecycle moves (show, unschedule, lock, unlock) and deletion are their own endpoints, never part of an edit.
- **Categories** and **difficulties**: manage the taxonomy challenges use.
- **Announcements**: post, edit, and remove the player live-feed announcements.
- **Event settings**: read and update the event's configuration, with the same version history and revert offered in the Settings UI. Updates are concurrency-checked, so a stale write is rejected rather than overwriting a newer change. The event's start, freeze, and end times are the one exception: because the end time also drives automatic teardown, an update or revert that changes any of the three is refused with HTTP `403`. Change the schedule from the Settings page instead.
- **Certificates**: register published certificate template versions with the event, issue credentials to each qualifying participant from the final standings, revoke a credential, and record that recipients have been emailed.

Standings you can change:

- **Score adjustments**: apply a manual bonus or penalty to a team, with a reason.
- **Leaderboard rebuild**: re-derive every team's rank and solve count from the event's recorded results and refresh each team's points from their recorded total. The response carries the number of teams it covered.

Data you can read:

- **Players**, **teams**, and the **leaderboard** (including top-team score progression). A player's **activity timeline** (their solves, attempts, hint unlocks, downloads, team changes and sign-ins in one ordered list) is available per player.
- **Submissions**, **stats**, and **analytics**: the figures behind the Overview and Analytics pages, including exports. Submission listings can optionally include the integrity findings that reference each attempt.
- **Challenge reports**: read report threads, post an organizer reply, and change a report's status.
- **Feedback**, **writeups** (with downloads), and running **challenge instances**.
- **Integrity**: list and open findings with their evidence, change a finding's review state, and manage the internal and test accounts that findings skip. The area also reports when the checks last ran and whether any are paused.

For the exact paths, fields, and filters in each area, consult the [API reference](/api).

The event's full data export is collected from **Data exports** in your organization dashboard, which stays reachable after the event has ended; see [Export event data](/organizers/how-to/export-event-data).

## Conventions

- **Errors** are returned with standard HTTP status codes.
- **Rate limits**: creating or publishing a challenge, and patching a challenge's own fields, are rate-limited; over the limit you get HTTP `429` with a message telling you how long to wait. Other endpoints aren't rate-limited.
- **Pagination** applies to the players, teams and submissions lists: pass `limit` and `offset`, and read `total` alongside the rows (`players`, `teams`, `submissions`) to page through. `limit` accepts 1–100 and defaults to 50; a value outside that range is clamped rather than rejected. All three take a `q` search term; players and teams also take `sort` (`name` or `points`) and `dir` (`asc` or `desc`), defaulting to name ascending for players and points descending for teams. The audit log, the integrity findings list and a player's activity timeline are paged the same way, with `limit` accepting 1–200. Remaining list endpoints return the full result set; some accept filters, such as a day range on time-series data or a status on reports.
- There is no version prefix in the URL; the current API is version 1.0.0.
