Skip to main content
GET
Start an OAuth connect
Redirects to the provider with _token, _workspace, and optionally _org in the query string. After consent, the provider calls back and the connection is created. See App connections. Redirects the browser to the provider’s consent screen. A browser navigation cannot set headers, so the scope rides the query string instead: _token (the bearer), _workspace (the workspace id), and optionally _org to connect at the organization level. After consent the provider calls back to /v1/apps/{provider}/callback and the browser lands on the dashboard’s /app-connect/{provider} page with status=success or status=error. Pass connectionId to re-authenticate an existing connection instead of creating a new one.
Availability: Cloud · Community (self-hosted) · Enterprise (self-hosted)

Authorizations

Authorization
string
header
required

A workspace API key (oc_…) or organization API key (oc_org_…). Workspace-scoped endpoints called with an organization key also need X-Workspace-Id.

Path Parameters

provider
string
required

App provider identifier (for example gmail, github, jira).

Query Parameters

_token
string

The bearer token, for browser navigations that cannot send Authorization.

_workspace
string

The workspace id, for browser navigations that cannot send X-Workspace-Id.

_org
string

Connect at the organization level (admin only). Prefer GET /org/apps/{provider}/authorize.

connectionId
string

Re-authenticate this connection.

agent_name
string

Carried through to the success redirect for the CLI's post-connect flow.

Response

Redirect to the provider's consent screen