Calendar
Calendar
Section titled “Calendar”Configures calendar settings including iCalendar limits and default names.
This object can be configured from the WebUI under Settings › Calendar & Contacts › Calendar
Fields
Section titled “Fields”defaultDisplayName
Section titled “defaultDisplayName”Type:
String?· default:"Stalwart Calendar"Specifies the default display name for a calendar when it is created
defaultHrefName
Section titled “defaultHrefName”Type:
String?· default:"default"Specifies the default href name for a calendar when it is created
maxAttendees
Section titled “maxAttendees”Type:
UnsignedInt· default:20· max: 100000Specifies the maximum number of attendees that can be included in a single iCalendar instance
maxRecurrenceExpansions
Section titled “maxRecurrenceExpansions”Type:
UnsignedInt· default:3000Specifies the maximum number of instances that can be generated from a recurring iCalendar event
maxICalendarSize
Section titled “maxICalendarSize”Type:
Size· default:"512kb"Specifies the maximum size of an iCalendar file that can be uploaded to the server
maxCalendars
Section titled “maxCalendars”Type:
UnsignedInt?· default:250· min: 1The default maximum number of calendars a user can create
maxEvents
Section titled “maxEvents”Type:
UnsignedInt?· min: 1The default maximum number of calendar events a user can create
maxParticipantIdentities
Section titled “maxParticipantIdentities”Type:
UnsignedInt?· default:100· min: 1The default maximum number of participant identities a user can create
maxEventNotifications
Section titled “maxEventNotifications”Type:
UnsignedInt?· min: 1The default maximum number of notifications a user can create for calendar events
JMAP API
Section titled “JMAP API”The Calendar singleton is available via the urn:stalwart:jmap capability.
x:Calendar/get
Section titled “x:Calendar/get”This is a standard Foo/get method as defined in RFC 8620, Section 5.1.
For singletons, the ids argument should be the literal singleton (or null to return the single instance).
This method requires the sysCalendarGet permission.
curl -X POST https://mail.example.com/api \ -H 'Authorization: Bearer $TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "methodCalls": [ [ "x:Calendar/get", { "ids": [ "singleton" ] }, "c1" ] ], "using": [ "urn:ietf:params:jmap:core", "urn:stalwart:jmap" ] }'x:Calendar/set
Section titled “x:Calendar/set”This is a standard Foo/set method as defined in RFC 8620, Section 5.3.
For singletons, only the update argument with id singleton is accepted; create and destroy arguments are rejected.
This method requires the sysCalendarUpdate permission.
curl -X POST https://mail.example.com/api \ -H 'Authorization: Bearer $TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "methodCalls": [ [ "x:Calendar/set", { "update": { "singleton": { "defaultDisplayName": "updated value" } } }, "c1" ] ], "using": [ "urn:ietf:params:jmap:core", "urn:stalwart:jmap" ] }'stalwart-cli wraps the same JMAP calls. See the CLI reference for installation, authentication, and general usage.
stalwart-cli get CalendarUpdate
Section titled “Update”stalwart-cli update Calendar --field defaultDisplayName='updated value'