MENU

Authentication

CMS-Tool supports OAuth 2.0 and legacy API ID/Key authentication.

  • OAuth Usage Instructions
    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 Client ID and Application Registration
    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
  • API Keys Authentication
    Legacy API ID/Key authentication is availble for private applications or software that cannot support an oAuth flow.