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

**Path:** `events/{event_id}/meeting-ratings`  
**Methods:** GET collection/record, POST, PATCH. There is no DELETE operation.

**GET**

- Fields: `event-id`, `meeting-id`, `registrant-id`, `score`, `comment`, `skipped`, `created-at`, `updated-at`.  
- Filters: `simple_rateable_id` (the meeting ID), `registrant_id`, `score`, `created_from`, `created_to`.  
- Associations: none.

```
GET .../meeting-ratings?simple_rateable_id=6001&score=5
```

**POST inputs:** `simple_rateable_id`, `registrant_id`, `score`, `comment`.

```json
{
  "simple_rateable_id": 6001,
  "registrant_id": 1201,
  "score": 5,
  "comment": "A useful conversation"
}
```

The meeting must be accepted, and the registrant must be a participant with an associated Brella user. POST is an upsert for the meeting and registrant pair. A score of `0` means skipped.

**PATCH** accepts `score` and `comment`. The meeting and registrant cannot be changed on an existing rating.