Create an email integration (an email account SysAid sends from, receives from, or both). The answer is 201 with the id of the new integration only; read it back with Get an Email Integration. Passwords and OAuth 2.0 client secrets are write-only and never returned or logged. lastModifiedDate is set by the gateway at the time of the request; id, dates and any property not listed in the request body are ignored. A create is not idempotent - repeating a request creates another integration. Creating with defaultOutgoing true makes the new integration the only default outgoing account. While SysAid blocks basic authentication for Microsoft (the disable-ms-basic-auth feature flag), an outgoing host or an incoming server on office365.com, outlook.com or exchange.microsoft.com is refused with 400; Microsoft accounts need OAuth 2.0 sign-in, which is set up in SysAid. A text value that sanitizing makes longer than SysAid can store is refused with 400 rather than cut. In rare cases SysAid stores the integration and still fails the request (when demoting the previous default outgoing account fails), which is answered 500; list the integrations before retrying. 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.
post
https://{account}.sysaidit.com/connect/v1/email-integrations
