---
title: "Fetch event by ID"
method: GET
path: "/api/v1/events/{event_id}"
tags: ["Proposals/Confirmed Bookings"]
---

# Fetch event by ID

`GET /api/v1/events/{event_id}`

## Request

- Base URL: `https://api.checkcherry.com`
- URL: `https://api.checkcherry.com/api/v1/events/{event_id}`
- Auth: none declared. Required headers: `Api-Key`

Returns the full details of a single event, including status, venue, pricing, and contact information.

Use the `include` query parameter to sideload related resources (comma-separated). Available: `event_bookings`, `proposal_alternatives`, `event_users`, `event_staff_members`, `event_staff_requests`, `contacts`, `notes`, `event_adjustments`. Nested includes are also supported — e.g. `?include=event_bookings.event_add_ons` will include add-ons within each booking. Other nested includes: `event_bookings.event_extras`, `event_bookings.event_photobooth_background`, `event_bookings.event_booking_extra_categories`, `proposal_alternatives.event_adjustments`. The event's customers are sideloaded via `event_users` — there is no `customer` include.

On a proposal with alternatives, `starting_balance`, `deposit_amount_due` and `balance_amount_due` add every alternative together, which is not a price the client pays. Read each alternative's totals instead.

**Required permission:** `assigned_event_read` or `unassigned_event_read`

## Path parameters

- `event_id` integer, required

## Query parameters

- `include` string

## Headers

- `Api-Key` string, required

## Response `200`

event found

---

[API](https://skmtc.dev/checkcherry/apis/check-cherry-business-api.md) · [All operations](https://skmtc.dev/checkcherry/apis/check-cherry-business-api/llms.txt) · [OpenAPI document](https://skmtc.dev/checkcherry/apis/check-cherry-business-api/revisions/84a9aabdf519?raw)