Update some settings of an email integration. Only the properties sent change; every property left out keeps its stored value, and so do the stored passwords, client secrets and private keys unless a new value is sent. The answer is 200 with the integration read back, in the shape of Get an Email Integration; credentials are never returned. lastModifiedDate is set by the gateway at the time of the request. Concurrent updates are not detected - the last write wins, for the whole record. A patch sends back every setting as it read it, so it undoes a change (a password, or defaultOutgoing given to another integration) saved by someone else in between. Changing an OAuth 2.0 integration's protocol to a non-OAuth 2.0 one clears its OAuth 2.0 settings in SysAid, and OAuth 2.0 settings patched on an integration that is not OAuth 2.0 are not kept. Setting defaultOutgoing true makes this the only default outgoing account; setting it false on the default one leaves none marked, and SysAid then sends from the lowest-id integration with outgoing enabled. While SysAid blocks basic authentication for Microsoft (the disable-ms-basic-auth feature flag), an integration whose outgoing host or incoming server is on office365.com, outlook.com or exchange.microsoft.com without OAuth 2.0 is refused with 400, also when the patch does not touch the host. A text value that sanitizing makes longer than SysAid can store is refused with 400 rather than cut. An id SysAid does not hold is answered 404. Requires a SysAid Admin session; SysAid administrators only. A request without a valid session is answered 401, and a signed-in user who is not a SysAid administrator is answered 403. A SysAid failure is answered 500 or 502; when it happens after SysAid stored the change, read the integration before retrying.
patch
https://{account}.sysaidit.com/connect/v1/email-integrations/
