# Issue with daily-usage-data Endpoint Returning 500 Error

**URL:** <https://forum.cursor.com/t/issue-with-daily-usage-data-endpoint-returning-500-error/153752>\
**Category:** Bug Reports\
**Tags:** teams-enterprise\
**Created:** [March 5, 2026, 7:40pm UTC](https://forum.cursor.com/t/issue-with-daily-usage-data-endpoint-returning-500-error/153752 "2026-03-05T19:40:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nishtha\_Arora](https://avatars.discourse-cdn.com/v4/letter/n/d07c76/32.png) [@Nishtha\_Arora](https://forum.cursor.com/u/Nishtha_Arora)\
**Post date:** [March 5, 2026, 7:40pm UTC](https://forum.cursor.com/t/issue-with-daily-usage-data-endpoint-returning-500-error/153752/1 "2026-03-05T19:40:23Z")

</div>

### Where does the bug appear (feature/product)?

Somewhere else…

### Describe the Bug

Hi Cursor Support Team,

I’m trying to access the [https://api.cursor.com/teams/daily-usage-data](https://api.cursor.com/teams/daily-usage-data) endpoint via Postman, but I consistently receive a 500 Internal Server Error.

For reference:

The teams/members endpoint works correctly.

The issue seems specific to the daily-usage-data endpoint.

I haven’t seen any announcements regarding downtime or issues with this endpoint.

Could you please confirm if there’s a known issue with daily-usage-data, or advise if there’s something I might be missing in the request?

this is what my request looks like

```auto
POST https://api.cursor.com/teams/daily-usage-data
500
301 ms
Warning: Self signed certificate in certificate chain
POST /teams/daily-usage-data HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Basic ****
User-Agent: PostmanRuntime/7.51.0
Cache-Control: no-cache
Postman-Token: ****
Host: api.cursor.com
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 104
 
{
"startDate": 1710720000000,
"endDate": 1710806400000,
"page": 1,
"pageSize": 1000
}
 
HTTP/1.1 500 Internal Server Error
Date: Thu, 05 Mar 2026 19:11:58 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
vary: Origin
access-control-allow-credentials: true
access-control-expose-headers: Grpc-Status, Grpc-Message, Grpc-Status-Details-Bin, Content-Encoding, Connect-Content-Encoding, traceparent, backend-traceparent, x-amzn-trace-id, x-request-id
Content-Length: 128
 
{"code":"internal","message":"There was an error processing your request. Please reach out to support if the problem persists."}

```

Thank you for your help!

### Steps to Reproduce

Call the endpoint with postman

### Expected Behavior

return 500 internal server error

### Operating System

Linux

### Version Information

2.4.31 (Universal)

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Nishtha\_Arora](https://avatars.discourse-cdn.com/v4/letter/n/d07c76/32.png) [@Nishtha\_Arora](https://forum.cursor.com/u/Nishtha_Arora)\
**Post date:** [March 5, 2026, 9:18pm UTC](https://forum.cursor.com/t/issue-with-daily-usage-data-endpoint-returning-500-error/153752/4 "2026-03-05T21:18:19Z")

</div>

Looks like the endpoint is back up

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [March 5, 2026, 9:58pm UTC](https://forum.cursor.com/t/issue-with-daily-usage-data-endpoint-returning-500-error/153752/5 "2026-03-05T21:58:37Z")

</div>

Hi @Nishtha_Arora!

Can confirm there were elevated errors on this endpoint, and the issue is resolved now. Sorry about that.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [March 27, 2026, 10:04pm UTC](https://forum.cursor.com/t/issue-with-daily-usage-data-endpoint-returning-500-error/153752/7 "2026-03-27T22:04:14Z")

</div>

Closed on March 27, 2026, 10:04pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.