A 500 on /teams/filtered-usage-events is usually about how the request is shaped rather than your account. Two quick things to check first:
Include a JSON body. If you send -H "Content-Type: application/json" with no body, the server rejects the empty payload and can return a 500. Send at least -d '{}', or better, your range: -d '{"startDate": 1748411762359, "endDate": 1751003762359}' (dates are epoch milliseconds).
Use a team-scoped API key. The /teams/* endpoints need a team key, not an org key — a scope mismatch can come back as a 500. See the Admin API docs.
If you’re already doing both and still hitting it, could you share:
the exact request body (date range + any filters — redact the key),
the approximate time in UTC of a failing call, and
whether it fails every time or only sometimes?
With that we can trace your specific request and dig in.