dataConnectors

Authorize a connection

Changed on

This method starts the OAuth authorization flow for a data connector. The platform returns an authorization URL. Redirect the user to this URL so they can grant access to their account.

After the user grants or denies access, the platform redirects them to the redirect URI you provided, with the outcome appended to that URI as query parameters. Read these parameters from the redirect that your application receives:

  • connection_id: The identifier of the new connection, returned on success. Store this value and pass it as the connection_id path parameter in later requests.
  • status: The ok value, returned on success.
  • custom_id: The label you supplied, returned on success when you provided one.
  • error: An error code, returned instead of the other parameters when the user denies access or the flow fails.
post/connections:authorize

Request

  • Base URL: https://api.twelvelabs.io/v1.3
  • URL: https://api.twelvelabs.io/v1.3/connections:authorize
  • Auth: API key in header x-api-key

Request body

provider'google_drive' required

The data connector provider to authorize.

redirect_uristring uri required

The URI where the user is redirected after granting or denying access. By default, any redirect URI is accepted. If you've authorized specific redirect URIs with the Register a redirect URI method, this URI must be one of them.

custom_idstring

A label you supplied, stored on the connection and returned with it. Use a value that does not identify a person so you can match the connection to your own records.

Response

The authorization flow has been successfully initiated.

authorize_urlstring

The URL to redirect the user to so they can grant access.

statestring

A value the platform uses to secure the authorization flow. You do not need to read or send it: the platform includes it in the authorize_url field and checks it automatically when the user is redirected back. It is returned only so you can match or troubleshoot requests.

Changes

  • b8591e05c0baRevision changes
    • warning

      deleted the header request parameter x-api-key

    • info

      the endpoint scheme security x-api-key was added to the API

  • 6205c7327cdeRevision changes
    • info

      api operation id authorize-connection removed and replaced with dataConnectors_authorize-connection