Issue with daily-usage-data Endpoint Returning 500 Error

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 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

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

Looks like the endpoint is back up

1 Like

Hi @Nishtha_Arora!

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

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