Eject a managed connector

Hex accent color (e.g., #000000) for branding.

Hex background color (e.g., #000000) for branding.

Provider-side URL for viewing or managing the resource represented by the connector. The destination can be an app, account, phone line, or service instance, depending on the connector type.

The connection method this connector was created from, when the create request named one.

Creation time in epoch milliseconds.

How the connector row was originally created. New create paths stamp this explicitly; older rows may omit it.

Installation used when a token request does not specify an installation.

Developer website for the connected service.

Human-readable connector name.

Developer documentation for the connected service.

Connector branding icon. SHA-1 hash that resolves to the uploaded icon through the Vercel avatar service. Consumers render this with https://vercel.com/api/www/avatar/{icon}.

Stable scl_ connector ID. Use this value directly in {connector}.

Whether the connector is known to have been edited since the app package it publishes to the provider was last built, so that package no longer matches it. Absent when it was not computed, or when the connector type publishes no such package. Derived on every read rather than marked at edit time, so reverting an edit clears it. Only reported by connector types that publish a package a user has to re-publish by hand — Microsoft Teams today.

Connector name within the owning team.

Redirect URI registered with the third-party service for this connector, if any. Used by startAuthorization/startInstallation to replay the exact URI back to the provider's token endpoint. Absent on connectors created before this field was introduced; those callers fall back to the https://connect.vercel.com/callback default.

Time when this connector started requiring reinstallation because an installation-affecting app-token grant changed.

Best-effort identifier of the third-party service this connector represents, independent of type. Examples: 'slack', 'mcp.linear.app', and 'auth.example.com'. Always present in API responses.

Provider logo from the known-service registry, matched by service. Often an SVG data URL. Absent when the service is not in the registry.

Whether the connector supports an installation flow.

Whether this managed connector can disconnect from its manager.

Whether Connect can revoke tokens for this connector.

Whether this connector type supports trigger webhooks. Derived from the type definition; indicates that triggers and triggerDestinations may be meaningful for this connector.

Which of the service's products/surfaces this connector points at.

Connector implementation type.

Icon identifier supplied by the connector type.

Human-readable name of the connector type.

Team-scoped UID. URL-encode this value before using it in {connector}.

Last update time in epoch milliseconds.

Public website for the connected service.