Reports PDF endpoint gives "502 Bad Gateway - NGINX" error since Dec 18. Is the endpoint broken?

Tech Discussions
,
1

Hi, I’ve been making nightly calls to the “https://api.track.toggl.com/reports/api/v3/workspace/{WORKSPACE_ID}/search/time_entries.pdf” endpoint for years (passing a start and end date), but as of December 18th these stopped working and consistently give a ““502 Bad Gateway - NGINX”” error.. Even the simple CURL examples from the API documentation are no longer working.

I’ve checked authentication etc and all seems OK, nothing has changed from the previous calls that have always worked. Is something broken on the server side?

Thanks in advance!

1 Like
2

can confirm the same for the non-pdf endpoint too

1 Like
3

Hello! Can you share if you are utilizing the calls as part of the email address you used to sign up for the community?

5

Yes I do! Same Email address.

6

I’m also experiencing a similar issue, but to a different endpoint: https://api.track.toggl.com/reports/api/v3/workspace/{$workspace_id}/projects/summary This has been happening to me for over a week, since at least 12/19/25.

I use a JS script that hits this endpoint occasionally (~3-4x/week) for a while w/o issue, but it started returning a 502 Bad Gateway response a couple of weeks ago, on 12/19. (Sorry, I don’t recall when it was last working, but it was probably earlier that week.) Same as reported above, I can’t even get the examples in the API docs to work:

❯ curl -X POST \
      https://api.track.toggl.com/reports/api/v3/workspace/{$workspace_id}/projects/summary \
      -H "Content-Type: application/json" \
      -u "{$email}:{$password}

as listed here: Summary reports | Toggl Engineering

7

Hello @Support team, just wondering if you have any update on this yet? This doesn’t seem to be an isolated problem. Thanks very much in advance!!

2 Likes
8

Heya! Our team is still investigating this. Once we have any updates we’ll be sure to let you know!

1 Like
9

I have the same situation with the endpoint: https://api.track.toggl.com/reports/api/v3/workspace/${workspaceId}/search/time_entries

I first noticed the problem on December 31, 2025. It occurred briefly, but after a while it started working again. It has been stopped working for me since January 5, 2026.

10

Hello! Our team has made some updates that we believe should help; can you all make another attempt and let us know if that’s helped?

1 Like
11

I tried it just now, and it worked!! Thank you so much! :heart_hands:

1 Like
12

Yes, same here: it seems to be working again. Thank you!

1 Like