BerriAI/litellm · error · HTTPException
Failed to initialize Vantage settings: {e}
Error message
Failed to initialize Vantage settings: {e} What it means
Catch-all 500 in the Vantage init endpoint: persisting the initial api_key/integration_token/base_url via _set_vantage_settings failed with an unexpected error (typically a database write or serialization problem). Original exception is logged first.
Source
Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:329
detail={"error": CommonProxyErrors.not_allowed_access.value},
)
try:
await _set_vantage_settings(
api_key=request.api_key,
integration_token=request.integration_token,
base_url=request.base_url,
)
verbose_proxy_logger.info("Vantage settings initialized successfully")
return VantageInitResponse(message="Vantage settings initialized successfully", status="success")
except HTTPException:
raise
except Exception as e:
verbose_proxy_logger.error("Error initializing Vantage settings: %s", e)
raise HTTPException(
status_code=500,
detail={"error": f"Failed to initialize Vantage settings: {e}"},
)
@router.post(
"/vantage/dry-run",
tags=["Vantage"],
dependencies=[Depends(user_api_key_auth)],
response_model=VantageExportResponse,
)
async def vantage_dry_run_export(
request: VantageDryRunRequest,
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
"""
Perform a dry run export using the Vantage logger.
View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check proxy logs for the underlying error and verify the init payload (API key, workspace) before retrying.
Defensive patterns
Strategy: try-catch
When it happens
Trigger: Thrown at litellm/proxy/spend_tracking/vantage_endpoints.py:329 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/85c5706c45fa40ef.
Report an issue: GitHub.