---
title: "Delete a Discord scheduled event"
method: DELETE
path: "/v1/discord/guilds/{guildId}/events/{eventId}"
tags: ["Discord"]
---

# Delete a Discord scheduled event

`DELETE /v1/discord/guilds/{guildId}/events/{eventId}`

## Request

- Base URL: `https://zernio.com/api`
- URL: `https://zernio.com/api/v1/discord/guilds/{guildId}/events/{eventId}`
- Auth: HTTP bearer

Hard-delete an event. Use PATCH with `status: 'cancelled'` instead
if you want the event preserved in the guild's history.

## Path parameters

- `guildId` string, required
- `eventId` string, required

## Query parameters

- `accountId` string, required

## Response `200`

Event deleted.

- object
  - `success` boolean
  - `deleted` string: The deleted event's snowflake.

## Other responses

- `401`: Missing or invalid API key. `code` is `missing_credentials` when no Authorization header was sent and `invalid_credentials` when the key is unknown, revoked or expired.
- `404`: Event or Discord account not found.
- `502`: Bot lacks MANAGE_EVENTS in the guild.

## Changes

- **2026-10-06** `f8c8f34fb41a`: 1 warning
  - added the new `account` enum value to the `details/budgetScope` response property for the response status `401`
- **2026-10-02** `d556591af3f6`: 7 info
  - added the optional property `code` to the response with the `401` status
  - added the optional property `details` to the response with the `401` status
  - added the optional property `docUrl` to the response with the `401` status
  - added the optional property `param` to the response with the `401` status
  - …3 more

[Operation history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/discord/guilds/:guildId/events/:eventId/delete.md)

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) · [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/4e74db179e73?raw)