Update Workspace Auth Connection
Update an auth connection
Headers
8 - 128Quoted version from auth connection management details
Your API key for programmatic access. Send it in the x-api-key header; you can create and manage keys from the Developers page.
Path Parameters
Body
- UpdateOAuth2ClientCredsRequest
- UpdateBasicAuthRequest
- UpdateBearerAuthRequest
- UpdateOAuth2JWTRequest
Updated auth connection fields
"oauth2_client_credentials"Response
Successful Response
- OAuth2ClientCredsResponse
- RefreshTokenAuthResponse
- BasicAuthResponse
- BearerAuthResponse
- OAuth2JWTResponse
- PrivateKeyJWTResponse
- MTLSAuthResponse
- CustomHeaderAuthResponse
- ApiIntegrationOAuth2AuthCodeResponse
- ApiIntegrationOAuth2CustomAppResponse
- WhatsAppAuthResponse
- SlackBotAuthResponse
- UrlSecretAuthResponse
Response model for oauth2 client creds
"oauth2_client_credentials"If True, send client credentials in Authorization header as Basic Auth instead of request body
Dependencies that use an auth connection
Single status field shared by every auth type's stored credential.
OAuth values (REFRESH_FAILED, REVOKED) are written by the OAuth
token-manager refresh path. CREDENTIAL_INVALID is written by the
tool execution path when an upstream response matches a credential's
failure_signatures entry (Bearer, Basic auth, etc.).
active, refresh_failed, revoked, credential_invalid Custom headers configured for OAuth2 token requests