Set recipient preferences for an event email context
Updates the recipient preference flags for all event emails in the given context (practitioner or facility). Preferences are stored at context scope and apply to both the credentialing and recredentialing modes — changing them here overrides any mode-level preference values. The request body contains four boolean flags: primaryEmail, caqhPrimaryEmail, credentialingPrimaryContact, and credentialingOfficeManager; each controls whether that recipient type receives event emails. Returns the full EventEmailSettingsContextResponse for the context. These same preferences can also be set as part of a full mode save via POST /{context}/{mode}. Note: this path does not constrain or validate context beyond requiring the recipientPreferences object in the body — other string context values are silently accepted.
Path parameters
Context (practitioner or facility)
Organization identifier that scopes this request to a specific organization's event email settings. Path segment; opaque string, no enforced format.
Headers
Tenant identifier of the requesting caller. Required on every request; opaque string, no enforced format.
Request body
Response
The full context settings record with the updated recipient preferences, including both mode summaries.
Changes
Changed in 1 of the 2 revisions of this API.24
- ●
added the new
inProgressenum value to thecredentialing/typeSettings/items/typeresponse property for the response status200response-property-enum-value-added
- ●
added the new
inProgressenum value to therecredentialing/typeSettings/items/typeresponse property for the response status200response-property-enum-value-added
- ○
added the media type
application/jsonfor the response with the status400response-media-type-added
- ○
added the media type
application/jsonfor the response with the status401response-media-type-added
- ○
added the media type
application/jsonfor the response with the status403response-media-type-added
- ○
added the media type
application/jsonfor the response with the status500response-media-type-added
This revision also has 44 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●