Sign inGet started
Docs
Get started

Google Slides API Authentication

How to authenticate Google Slides API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes tokens for you.

Every Google Slides API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Google Slides account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a Google Slides connection in Connections. Google Slides uses OAuth. When you create the connection, you are redirected to sign in to Google Slides and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
  4. Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Google Slides account that should run the action. MindCloud stores and refreshes the Google Slides credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Get Presentation with an Google Slides connection looks like this:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/googleSlides/latest/actions/get-presentation" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Google Slides account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Google Slides

You need access to a Google Cloud project where you can enable APIs, configure the Google Auth platform, and create OAuth client credentials for a web application.

  1. Open Google Cloud Console

    Sign in to Google Cloud Console with the account that owns the Google Slides integration project.

  2. Select or create the Google Cloud project

    Use the project that will own the Google Slides API and OAuth client for this MindCloud connector.

  3. Enable the Google Slides API

    Enable the Google Slides API in the selected project before creating OAuth credentials.

  4. Configure the OAuth consent screen in Google Auth platform

    In Google Cloud Console, go to Google Auth platform > Branding and complete the app information, support email, audience, and contact information flow. If Google Auth platform is not configured yet, click Get Started and finish the setup flow.

  5. Add test users if the app is External and still in Testing

    If you selected External for the audience and the app is not yet published, go to Google Auth platform > Audience and add the operator email address as a test user before attempting the connection.

  6. Add the connector scopes in Data Access when required

    If this app is used outside of your organization, go to Google Auth platform > Data Access and add the scopes requested by this connector so the consent screen matches the requested access.

  7. Create a Web application OAuth client

    Go to Google Auth platform > Clients, click Create Client, choose Application type > Web application, and create a client for the MindCloud Google Slides connector.

  8. Add the authorized redirect URI

    Under the Web application client, add this authorized redirect URI exactly: https://api.mindcloud.co/v1/oauth/googleSlides/callback

  9. Copy the client ID and client secret into MindCloud

    Use the generated client ID and client secret when creating the MindCloud connection, then complete the Google consent flow in MindCloud.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.