Save event email settings for one context and mode
POST/organizations/:organizationId/event-email-settings/:context/:mode
Creates or replaces event email settings for the given context and mode (upsert — if no record exists it is created, if one exists it is fully replaced). Both context and mode are matched against a case-sensitive route pattern — other casings return 404 at the routing layer before this operation executes. The request body should include a typeSettings array covering all six event-type values (initiated, approved, denied, cancelled, psvReady, inProgress), though this is not enforced by the server; any type with enabled: true must supply a non-blank template.subject and template.bodyHtml, otherwise the server returns 400. recipientPreferences is persisted at the context level and is shared across both modes for that context — changing it here also affects the other mode. Returns the full updated settings record. For updates only, PUT /{context}/{mode} is available and invokes this same upsert logic.
Request
Responses
- 200
- 400
- 401
- 403
- 500
The full event email settings record after the create/replace, including resolved recipient preferences, ccEmail, logoUrl, logoWidth, and per-type template settings.
A typeSettings entry has enabled: true but is missing template.subject or template.bodyHtml.
Unauthorized - Authentication required
Forbidden - User does not have required permissions
Internal Server Error