Update a provider configuration
Update the supplied fields; omitted fields remain unchanged. Names must remain unique within the organization. Requires an organization-scoped credential or dashboard authentication; project-scoped credentials receive 403.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Provider configuration ID or name in the organization.
Body
Update a provider configuration. Omitted fields are left unchanged. Renaming preserves wallet bindings. Credential updates apply to all wallets using this configuration. Provider and client ID are immutable; changing clients requires a new configuration. The selected configuration determines how credentials are validated; its identity and mode must not change during secret rotation.
Response
Provider configuration updated without returning secrets
- Option 1
- Option 2
Response schema for a Link configuration, without secret credentials. Kernel generates the ID and timestamps. Configuration creation uses VaultLinkProviderConfigRequest.
OAuth client identity; immutable. Secret credentials are never returned.
Unique within the organization.
^[a-zA-Z0-9._-]{1,255}$link