Calendar Event Types

An event type is a lightweight category that calendar entries are grouped under (e.g. "Meeting", "Customer information"). These endpoints manage the types themselves; assign one to an entry via calendar_event_type_id.

Required scope: read:calendar_event_types, write:calendar_event_types.

Endpoints

Types created via the API are published immediately and available to assign. Only published types are visible here: a type that is unpublished in the CMS is left out of the list, and GET or PATCH on its id returns 404. Event types cannot be deleted via the API.

Translations

Event type names are translatable. name reads and writes the customer's default content locale (on read it falls back to the first translated name when the default locale has none); the optional translations object holds per-locale names (e.g. { "en": "Customer information" }). Locale keys must be languages activated on the platform — discover them via GET /locales; unknown or inactive locales return 422.

List

curl "https://customer.monotree.com/api/open/v1/calendar-event-types" \
  -H "Authorization: Bearer mono_your_token_here"

Newest first.

Create

curl -X POST https://customer.monotree.com/api/open/v1/calendar-event-types \
  -H "Authorization: Bearer mono_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Kunde information", "translations": { "en": "Customer information" } }'

Request body

Returns 201 with the event type. PATCH accepts the same fields — all optional. name renames the default content locale; translations sets or updates specific locales.

Response

{
  "data": {
    "id": 2,
    "name": "Kunde information",
    "translations": { "da": "Kunde information", "en": "Customer information" },
    "created_at": "2026-07-03T10:00:00+02:00",
    "updated_at": "2026-07-03T10:00:00+02:00"
  }
}