---
title: "Get current epoch"
method: GET
path: "/v1/points/epoch/current"
tags: ["Points"]
---

# Get current epoch

`GET /v1/points/epoch/current`

Get the next upcoming scheduled points drop (by distribution_at), plus the countdown to it. Ad-hoc epochs are never returned here. Returns no epoch (not an error) when no upcoming drop is scheduled.

## Response `200`

A successful response.

- ApiGetCurrentEpochResponse
  - `epoch` ApiPointsEpochDto — PointsEpochDto is an epoch's schedule. ends_at/distribution_at are 0 when unset.
    - `epoch_id` string
    - `starts_at` string, int64 — 0 = unset. Deprioritized: distribution_at is what drives reveal/countdown, starts_at is purely descriptive (e.g. does not apply to a retroactive drop).
    - `ends_at` string, int64
    - `distribution_at` string, int64 — 0 = unset. Points ingested for this epoch are invisible on every public read until now >= distribution_at.
    - `description` string
    - `is_adhoc` boolean — An ad-hoc (one-off/retroactive) drop still schedules and reveals normally, but is excluded from GetCurrentEpoch's "next upcoming drop" selection so it never overrides the frontend's weekly countdown.
  - `seconds_until_distribution` string, int64

## Other responses

- `default` — An unexpected error response.

---

[API](https://skmtc.net/rise/apis/risex-rest-api.md) · [All operations](https://skmtc.net/rise/apis/risex-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/rise/risex-rest-api/revisions/194af8339c0d/schema)