# DELETE /api/v2/events/{event}

Delete an event

- MCP id: events.destroy
- Scope: api:destroy:events
- Permission: events::manage_self
- Rate cost: 1 unit, write bucket.
- Cache-Control: private, no-store

Soft-deletes an event; `POST events/{event}/actions/restore` reverses it. ⚠ On a recurring master this removes the whole series (every occurrence disappears), where plnnrly would have asked "this occurrence / this and following / all".

There is no `force` parameter: this resource is not force-deletable, so `?force=true` is a `400` `unsupported-parameter`. Deleting an event that is already deleted answers `204` as well, so a retry is safe. Any time already logged against the event's task is unaffected. Known gap: unlike plnnrly, an API delete does not push the removal to open agenda tabs, so a colleague with the calendar open may keep seeing the event until they reload.

## Parameters
- event (integer, path): The Event's numeric id. Accepts a soft-deleted record.
- X-Request-Id (header, optional): A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
- If-Match (header, optional): The ETag a write is conditional on. A stale validator is 412 precondition-failed.

## Response 204

## Errors
- 403 forbidden-by-policy | insufficient-permission | insufficient-token-scope: Forbidden.
  - `forbidden-by-policy`: The event is your own and you hold `events::manage_for_others` but not `events::manage_self`. Another user's event answers `404` instead when you do not hold `events::manage_for_others`, because you cannot see it.
- 412 precondition-failed: Precondition failed.
- 400 idempotency-key-required | invalid-cursor | invalid-query-parameter | malformed-request | unsupported-parameter: Bad request.
- 401 token-expired | unauthenticated: Unauthenticated.
- 404 endpoint-not-found | resource-not-found: Not found.
- 406 not-acceptable: Not acceptable.
- 429 rate-limit-exceeded: Too many requests.
- 500 internal-error: Server error.
- 503 tenant-unavailable: Service unavailable.

## Example
```bash
curl -X DELETE \
  'https://<your-url>/api/v2/events/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'
```