Skip to content
  • There are no suggestions because the search field is empty.

Using OAuth Authentication

OAuth 2.0 authentication allows third-party applications and services to connect to SlickText without requiring users to share their passwords. Instead, users authorize access through a secure, token-based flow.

OAuth can help developers and organizations:

  • Build third-party integrations using the SlickText API
  • Connect partner applications with explicit user consent
  • Authenticate internal tools and scripts securely
  • Maintain better visibility and control over connected applications

In this article:

How OAuth 2.0 Works
Registering and Managing an OAuth Application
Security and Compliance


How OAuth 2.0 Works

OAuth 2.0 lets you authorize an application to access your SlickText account without sharing your password.

At a high level, the process works like this:

  1. You start connecting a third-party application to SlickText.
  2. SlickText asks you to review the permissions the application is requesting.
  3. You approve or deny the request.
  4. If you approve the request, SlickText redirects you back to the application.
  5. The application receives authorization credentials that it can exchange for an access token.
  6. The application uses the access token to make authorized API requests.

Access tokens allow applications to interact with SlickText based on the permissions you approved

Registering and Managing an OAuth Application

To register an OAuth application, reach out to SlickText Support.

When registering an OAuth application, you’ll need to provide information such as:

  • Application name
  • Redirect URI
  • Logo URI
  • Application description

After an OAuth application is registered, users can authorize the application through the OAuth consent flow.

If you need to make adjustments to your OAuth application settings, reach out to SlickText Support.

Security and Compliance

OAuth 2.0 helps reduce risk by allowing integrations to authenticate with tokens instead of shared passwords.

OAuth access can supports stronger security practices, including:

  • Access tokens expire after 1 hour.
  • Refresh tokens do not expire.
  • Tokens are transmitted over HTTPS.
  • Applications can revoke a token using the revoke endpoint: https://dev.slicktext.com/v1/oauth/revoke.
  • Users can revoke authorized application access from the Authorized Apps section on the integrations page in SlickText.