Using OAuth 2.0 with Engagement Cloud (a non-developer's guide)

This is a non-developer's guide as to what is achievable using OAuth 2.0. Read a technical guide for integrating to Engagement Cloud with OAuth 2.0 in our developer hub.

Engagement Cloud uses OAuth 2.0 to provide 'single sign-on'. Single sign-on provides the means for an Engagement Cloud user to log into their account without the need for them to constantly re-enter their credentials. When they wish to use their Engagement Cloud account, they just click through from their CRM, extranet or other platform.

This process requires a way of authenticating your users that is accessible over the internet, and an amount of development work (detailed in our developer's guide to using OAuth 2.0 with Engagement Cloud).

To protect all our customers' email sending reputations, this is not available by default. Customers wishing to enable this functionality must contact their account manager and will be asked to go through an approvals process.

Note for Corporate and Reseller accounts

Registering your main Engagement Cloud account for OAuth access will by default enable all your child accounts for OAuth authentication. Any new accounts just need to complete the initial authorisation phase before obtaining an access and refresh token. 

You will need to have an SSL certificate for your application domain. If you do not have one already, please speak to your account manager about buying one.

Have more questions? Submit a request

Comments