---
title: "Events"
description: "Events: available fields, filters, associations, and API operations."
lastModified: "2026-08-21"
---

**Path:** `events` at organization level, for example `/api/core/organizations/30/events`  
**Methods:** GET collection/record, PATCH. DELETE is available only in sandbox. POST is never available to Core organization tokens.

**GET**

- Fields: `name`, `start-date`, `end-date`, `join-code`, `public-code`, `event-type`, `registrant-count`.  
- Filter: `event_type`.  
- Associations: `timeslots` and `organization`, both linkage-only with no configurable association attributes.  
- Row restriction: `event_type` may be restricted by the administrator. The scope's event selection also limits this collection.

```
GET /api/core/organizations/30/events?event_type=in_person
GET /api/core/organizations/30/events/319986
```

**PATCH inputs:** `name`, `start_date`, `end_date`.

```json
{
  "name": "Customer Summit 2027",
  "start_date": "2027-04-12",
  "end_date": "2027-04-14"
}
```

Event creation is not supported because the Core token has no acting user to own the event. Event deletion is removed from introspection and rejected outside a sandbox environment.