---
title: "Abuse reports"
description: "Create and update abuse reports with complete curl request examples."
lastModified: "2026-08-25"
---

**Collection path:** `events/{event_id}/abuse-reports`

| Input | Type | POST | PATCH | Notes |
| :---- | :---- | ----: | ----: | :---- |
| `reported_registrant_id` | Scalar ID | Required | Ignored | Reported registrant must belong to the event and have a Brella user. |
| `reporting_registrant_id` | Scalar ID | Required | Ignored | Reporting registrant must belong to the event and have a Brella user. |
| `reason` | Scalar string or `null` | Optional | Ignored | Reason recorded on the report instance. |
| `status` | Scalar string | Ignored | Required for a meaningful update | PATCH accepts only `archived` or `solved`. |

## POST an abuse report

Repeated reporting of the same user is handled by Brella's report service and may update the existing parent report rather than creating an unrelated duplicate.

```shell
curl --request POST \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/abuse-reports" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "reported_registrant_id": 1201,
    "reporting_registrant_id": 1202,
    "reason": "Unwanted contact"
  }'
```

The response type is `abuse-report`. Useful write-response fields include `reported_registrant_id`, `report_count`, and `latest_report_at`.

## PATCH an abuse report

The status update is applied to all report instances represented by the parent abuse report.

```shell
curl --request PATCH \
  --url "${BRELLA_API_BASE_URL}/api/core/organizations/${BRELLA_ORGANIZATION_ID}/events/${BRELLA_EVENT_ID}/abuse-reports/7001" \
  --header "Accept: application/vnd.brella.v4+json" \
  --header "Brella-API-Access-Token: ${BRELLA_API_ACCESS_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-raw '{
    "status": "solved"
  }'
```