---
title: "Update Hashicorp Vault Config"
method: POST
path: "/config_overrides/hashicorp_vault"
tags: ["Config Overrides"]
---

# Update Hashicorp Vault Config

`POST /config_overrides/hashicorp_vault`

Update Hashicorp Vault secret manager configuration.
Sets environment variables, encrypts sensitive fields, and stores in DB.
Reinitializes the secret manager on this pod.

## Request body

- HashicorpVaultConfig — Configuration for Hashicorp Vault secret manager integration.
  - `vault_addr` string, nullable — The address of the Vault server (e.g., https://vault.example.com:8200)
  - `vault_token` string, nullable — Token for Vault token-based authentication
  - `approle_role_id` string, nullable — Role ID for Vault AppRole authentication
  - `approle_secret_id` string, nullable — Secret ID for Vault AppRole authentication
  - `approle_mount_path` string, nullable — Mount path for the AppRole auth method (default: approle)
  - `client_cert` string, nullable — Path to the client TLS certificate for Vault
  - `client_key` string, nullable — Path to the client TLS private key for Vault
  - `vault_cert_role` string, nullable — Certificate role name for TLS cert authentication
  - `vault_namespace` string, nullable — Vault namespace (for multi-tenant Vault, sent as X-Vault-Namespace header)
  - `vault_mount_name` string, nullable — KV engine mount name (default: secret)
  - `vault_path_prefix` string, nullable — Optional path prefix for secrets (e.g., myapp -> secret/data/myapp/{secret_name})

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/sea-lion/apis/litellm-api.md) · [All operations](https://skmtc.net/sea-lion/apis/litellm-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sea-lion/litellm-api/revisions/79928a3d37d3/schema)