OAuth 2.0 is recommended for new integrations. It allows a CMS-Tool user to authorise an application for a selected website without giving that application the user's CMS password or permanent API key. Access can be limited using scopes, tokens are short-lived, and the OAuth connection can be disconnected by the website owner or administrator.
OAuth applications need a client ID before they can start a CMS-Tool OAuth authorization request. Our platform supports CIMD and manual registration of your redirect URI