### Check for existing issues

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

### What happened?

**Issue**

The logs page shows the banner "Request/Response Data Not Available" for requests whose `request_id` contains a `#` character. This happens even though prompt storage is enabled and the data is stored correctly in the `LiteLLM_SpendLogs` table (`proxy_server_request` and `response` columns are populated).

LiteLLM uses the upstream provider's response `id` as the spend-log `request_id`. Our OpenAI-compatible (https://aki.io/) provider returns IDs like:

``` chatcmpl-31ab33ad-0c19-4711-b857-6cca19462ca2#114034 ```

**Root cause**

`uiSpendLogDetailsCall` interpolates the raw `logId` into the URL path without percent-encoding (while `start_date` is encoded): ```ts let url = proxyBaseUrl ? `${proxyBaseUrl}/spend/logs/ui/${logId}?start_date=${encodeURIComponent(start_date)}` : `/spend/logs/ui/${logId}?start_date=${encodeURIComponent(start_date)}`; ``` Source: https://github.com/BerriAI/litellm/blob/v1.91.0/ui/litellm-dashboard/src/components/networking.tsx#L4806

Everything from the first `#` is a fragment and is never sent to the …