Delete an event
Deletes an event that has no held or booked seats, together with its seat history. Refused with `409 event_has_reservations` while any seat is booked or held (expired holds do not count) — release them first. The bound chart is unaffected.
curl -X DELETE "https://seatbuilder.org/api/v1/events/string"{
"eventKey": "evt_q3-2026-jazz-night",
"deleted": true
}{
"statusCode": 0,
"error": "string",
"message": "string",
"code": "validation_failed",
"failed": [
{
"objectLabel": "string",
"reason": "string",
"eventKey": "string",
"environment": "string",
"booked": 0,
"held": 0
}
],
"errors": {
"property1": [
"string"
],
"property2": [
"string"
]
}
}{
"statusCode": 0,
"error": "string",
"message": "string",
"code": "validation_failed",
"failed": [
{
"objectLabel": "string",
"reason": "string",
"eventKey": "string",
"environment": "string",
"booked": 0,
"held": 0
}
],
"errors": {
"property1": [
"string"
],
"property2": [
"string"
]
}
}{
"statusCode": 0,
"error": "string",
"message": "string",
"code": "validation_failed",
"failed": [
{
"objectLabel": "string",
"reason": "string",
"eventKey": "string",
"environment": "string",
"booked": 0,
"held": 0
}
],
"errors": {
"property1": [
"string"
],
"property2": [
"string"
]
}
}{
"statusCode": 0,
"error": "string",
"message": "string",
"code": "validation_failed",
"failed": [
{
"objectLabel": "string",
"reason": "string",
"eventKey": "string",
"environment": "string",
"booked": 0,
"held": 0
}
],
"errors": {
"property1": [
"string"
],
"property2": [
"string"
]
}
}Update an event PATCH
Updates an event's `name`. The bound chart cannot be changed here; to give this event its own chart, use `POST /events/{eventKey}/actions/move-to-new-chart-copy`.
Move an event to a new copy of its chart POST
Detaches one event from a chart shared with other events. Copies the chart's **published** version (the layout this event shows now; an unpublished draft is not included) into a new, already published chart named `<chart name> (<eventKey>)`, and binds the event to it. Holds, bookings and GA quantities stay as they are, and the layout is identical, so buyers see no change. From then on, republishing either chart no longer affects the other: edit and publish the new chart (the response's `chartKey`) to change this event only. Sends an `event.chart_changed` webhook. The new chart counts toward your plan's chart limit. Not for use inside a ticket-sales flow.