---
title: "Retrieve a round"
method: GET
path: "/round/{round_slug}"
tags: ["Round"]
---

# Retrieve a round

`GET /round/{round_slug}`

Retrieves the round identified by the specified slug.

## Headers

- `Accept` 'application/vnd.Creative Force.v2.3+json' | 'application/vnd.Creative Force.v2.3+xml', required
- `x-api-language` string[]

## Response `200`

Round retrieved.

- Round — Single round: a phase of a season with its own type, dates, form, and chapters.
  - `chapters` object[] — Chapters associated with the round.
    - `slug` string — Short URL-safe identifier for the chapter.
    - `link` string, uri — Canonical URL for the chapter resource.
    - `name` object — Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string.
  - `created` string, date-time — Date and time the round was created, in ISO 8601 format.
  - `end_date` string, nullable — Date and time the round closes, in `YYYY-MM-DD HH:MM:SS` format. This value carries no timezone offset. `null` when no close date is set.
  - `form` string — Slug of the form associated with the round.
  - `name` object — Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string.
  - `season` object — Season the round belongs to.
    - `slug` string — Short URL-safe identifier for the season.
    - `link` string, uri — Canonical URL for the season resource.
    - `name` object — Map keyed by locale code (for example, `en_GB` or `fr_FR`). Keys are drawn from the languages enabled on the account. Values are the translated string.
  - `slug` string — Short URL-safe identifier for the round.
  - `start_date` string, nullable — Date and time the round opens, in `YYYY-MM-DD HH:MM:SS` format. This value carries no timezone offset. `null` when no open date is set.
  - `type` 'entry' | 'judge' | 'feedback' — Type of the round.
  - `updated` string, date-time — Date and time the round was last updated, in ISO 8601 format.

## Other responses

- `400` — Request was rejected before the endpoint could process it. Common causes: invalid `Accept` header, unsupported `x-api-language` code, empty request body on `POST` / `PUT`, or invalid JSON in the request body.
- `401` — Missing `x-api-key` header.
- `403` — Authenticated request denied. Common causes: invalid or unknown API key, suspended account, or `api` feature not enabled for the account.
- `404` — Resource identified by the path slug does not exist. Returned when the slug is well-formed but no record matches it.
- `429` — Rate limit of 60 requests per minute exceeded.
- `503` — Service is temporarily unavailable due to regional maintenance.

---

[API](https://skmtc.dev/tectonic/apis/award-force-api.md) · [All operations](https://skmtc.dev/tectonic/apis/award-force-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/tectonic/award-force-api/revisions/21f74cd75a05/schema)