Skip to main content

Event dates

An event has one or more EventDate rows — start/end pairs representing the slots people get tickets to. Multi-day events use multiple dates; a single-evening event uses one. All three mutations are restricted to draft events.

All mutations on this page require a JWT — get one from the homepage first. The API key needs the events:write scope.

Add an event date​

Creates a new date and attaches it to the event. If the event already has ticket specifications, the new date is automatically associated with each one — so existing SKUs grant access to the new slot too.

mutation addEventDate($input: AddEventDateInput!) {
addEventDate(input: $input) {
  eventDate {
    id
    startDateTime
    endDateTime
  }
}
}

Validation:

  • endDateTime must be strictly after startDateTime.
  • Event must not be completed or published.

Edit an event date​

Update start/end on an existing date.

mutation editEventDate($input: EditEventDateInput!) {
editEventDate(input: $input) {
  eventDate {
    id
    startDateTime
    endDateTime
  }
}
}

The input takes both eventId (validated against your organization) and id (the event-date row to edit). Pass both — the server uses id for the lookup but checks the date belongs to an event your org owns.

Remove an event date​

mutation removeEventDate($input: RemoveEventDateInput!) {
removeEventDate(input: $input) {
  success
}
}

Errors:

  • Event-date with id: <id> not found.
  • Cannot remove date from an event, which is completed / …which has already been published.