6 views
-/https://github.com/berriai/litellm/issues/32695
GitHub Ā· issue

#32695 [Bug]: Minor - OpenAPI documentation shows incorrect keys for budget_limits

  • State: open
  • Author: @icsy7867
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

In several places in the swagger pages I see: ``` budget_limits: Optional[list] - List of concurrent budget windows for the key. Each window specifies a budget_limit, time_period, and optional budget_duration. Example - [{"budget_limit": 10.0, "time_period": "1d"}, {"budget_limit": 50.0, "time_period": "7d"}]. ```

However this kept failing in my curl request. I checked litellm docs: https://docs.litellm.ai/docs/proxy/users

``` curl 'http://0.0.0.0:4000/key/generate' \ --header 'Authorization: Bearer <your-master-key>' \ --header 'Content-Type: application/json' \ --data-raw '{ "budget_limits": [ {"budget_duration": "24h", "max_budget": 10}, {"budget_duration": "30d", "max_budget": 100} ] }' ```

This worked.

### Steps to Reproduce

Use the incorrect keys, suffer...

### Relevant log output

```shell This was from my code:

[Thu Jul 09 23:16:56.388431 2026] [php:notice] [pid 17:tid 17] [client 172.16.93.176:45214] HTTP error in generateRateLimitedKey: 422 - {"detail":[{"type":"missing","loc":["body","budget_limits",0,"budget_d…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 Ā· 31d18h28m18s ago — entered Ā· #import:https:::github.com:berriai:litellm post #2405
The right issue is substantially harder: it requires a configurable cross-cutting request-flow behavior, safe defaults, failure classification, integration coverage, and security-sensitive testing. The left issue is primarily a localized schema/documentation consistency fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search