Why does the /v1/dashboard/billing/usage endpoint now require a session key?

Below is an explanation:

What's Happening

The error indicates that the endpoint now expects a session key (provided by a logged-in browser session) rather than a secret API key. This change means that the /v1/dashboard/billing/usage endpoint is now intended only for interactive use via the OpenAI platform dashboard and not for programmatic access with secret keys.

What Changed?

Previously, developers might have been able to call this endpoint using a secret API key to fetch billing usage details. Now, OpenAI has restricted the endpoint so that billing usage data can only be accessed with a session key. This improves security by ensuring that sensitive billing information is only exposed in a trusted web session.

What Should You Do?

• For programmatic usage:
  If you need to monitor API usage programmatically, refer to the Usage page in the OpenAI Platform, which displays tracked usage data once enabled. Note the guidelines regarding tracking for keys generated before and after December 20, 2023.

• For interactive use:
  Use the browser and log in to your OpenAI account to access the dashboard endpoints.

Code Example

If you were previously using a secret key like this:

BASHCopied
curl https://api.openai.com/v1/dashboard/billing/usage \
  -H "Authorization: Bearer YOUR_SECRET_KEY"

You now need to access this page via your browser session instead.

Conclusion

The /v1/dashboard/billing/usage endpoint remains available but is now restricted to be accessed only with a session key (i.e., through the browser). It is no longer intended for direct programmatic access using secret API keys. For development purposes, use the designated Usage page and follow the updated best practices for managing usage data.