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
Body
Update a provider configuration. Omitted fields are left unchanged. Renaming preserves item 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. A VGS configuration's vault_id and environment are immutable too: rotating its client_secret repeats the aliases:read and vault checks against the same vault and environment.
Response
Provider configuration updated without returning secrets
- Option 1
- Option 2
- Option 3
Response schema for a Link configuration, without secret credentials. Kernel generates the ID and timestamps. Configuration creation uses VaultLinkProviderConfigRequest.