Publish a new version of connector
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Authentication protocol used by the connector.
integration-app-token, membrane-token, oauth2, oauth1, client-credentials, proxy Additional JSON Schema for workspace-level overrides of credentials (e.g. BYO-OAuth clientId/clientSecret).
JSON Schema for end-user input collected during connection (e.g. an API key or subdomain the user types in).
Function that derives auth credentials from connection parameters. Use for static-key auth (api-key, basic-auth) where the user-provided input IS the credential.
Function that refreshes expired credentials. Implement for non-standard OAuth refresh flows or when additional credentials need to be refreshed alongside the OAuth token.
Function that configures the authenticated HTTP client used by connector API requests and actions. Typically a mapping type with baseUri and auth header wiring.
OAuth2: function returning { authorizeUri, tokenUri, scopes, noRefreshToken? } — the authorize/token endpoint URLs and requested scopes.
OAuth2: function invoked with the raw token response to extract token metadata. Rarely needed.
OAuth2: function that transforms the token endpoint response into the final credentials object. Required for multi-tenant APIs (Microsoft) or APIs that require post-OAuth bootstrap calls.
OAuth2: function that transforms the refresh token endpoint response into the refreshed credentials. Required when refresh responses differ from initial-token responses.
Function that verifies the connection by making a lightweight authenticated API call (typically a rest-api-mapping against a /me-style endpoint).
Function that revokes credentials at the provider when the connection is removed. Implement only if the provider exposes a revoke endpoint.
For type: "proxy" — identifies which proxy configuration the workspace should use.