---
title: "REST API: Delete Event"
type: "wiki"
space: "Axero Documentation"
author: "Anonymous User"
created: 2011-03-28T07:06:20Z
updated: 2026-09-28T01:10:25Z
tags: ["API"]
url: "https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/492/rest-api-delete-event"
---

# REST API: Delete Event

[Open API Guide](https://my.axerosolutions.com/spaces/5/axero-documentation/api-guide?id=492)
DELETE/api/events/\{EventID\}

Permanently remove an event from the intranet calendar by its ID. This deletes the event along with its attendee list, reminders, and associated RSVP data.

## Request

### Request Header
| Header | Required | Value | Description |
| :--- | :--- | :--- | :--- |
| `Authorization` | YES | `Bearer YOUR_TOKEN` | Bearer token for the authenticated user. [Learn how to create Bearer tokens](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens). |
### Required Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `EventID` | Integer | YES | Path | Unique identifier for a particular event |
### Optional Parameters
| Parameter | Type | Required | Location | Description |
| :--- | :--- | :--- | :--- | :--- |
| `SendNotifications` | Boolean | NO | Query | Whether to send invited users and attendees a cancellation notification. Set as true or false. Default is true. |
| `InstanceOption` | Integer | NO | Query | For a recurring event, which occurrences to delete: 1 = All \(default\), 2 = Future, 3 = Single. |
| `Instance` | String | NO | Query | For a recurring event, the start date and time of the occurrence the deletion applies to when InstanceOption is 2 or 3. Give it in ISO 8601 form in UTC \(for example 2026-10-01T14:00:00Z\). A value that cannot be read as a date answers 500 and deletes nothing. Default: none. |
## Example

### Request Header

```
Authorization: Bearer YOUR_TOKEN
```

### Request URL

`https://your-site.com/api/events/23`

### Success Response

```
{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": true
}
```

### Error Response

```
{
  "Message": "The request is invalid."
}
```

## Error Handling

| Status Code | Likely Cause | Next Action |
| :--- | :--- | :--- |
| 400 Bad Request | EventID in the path is not an integer. | Send the event's numeric ID. |
| 401 Unauthorized | Missing or invalid Bearer token. | Check token validity. [Learn how to create Bearer tokens →](https://my.axerosolutions.com/spaces/5/axero-documentation/wiki/view/108973/creating-bearer-tokens) |
| 403 Forbidden | User does not have sufficient permissions. | Confirm the user has the required roles for this action. |
| 500 Server Error | Internal failure. An Instance value that cannot be read as a date also answers 500, and the event is not deleted. | Retry later. If the request carried an Instance value, check its format first. |
| 200 with ResponseData false | EventID is 0, or the event could not be deleted. | Check the EventID and the caller's rights on the event. |

## Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

- **Sustained Request Rate:** Do not exceed 5 API calls per second
- **Sequential Processing:** Wait for each request to complete before sending the next in automated workflows
- **Concurrent Connections:** If parallel processing is required, limit to 3 or fewer simultaneous requests
- **Response Timeout:** Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.