paigen11 is trying to access Discourse reports via Pipedream to send data to Segment. While the initial API call works, attempts to access /admin/reports/signups.json result in a 404 error, despite the URL working in a browser. pfaffman suggests checking API credentials and headers, referencing the Discourse API Documentation. paigen11 resolves the issue by generating an API key tied to an admin account, noting that the documentation may need clarification on permission levels for different API routes.
I’m trying to pull Discourse report info via Pipedream so I can send it to Segment for analytics purposes.
The Pipedream integration with Discourse works when I run the starting query of https://${auths.discourse.domain}/admin/users/list/active.json with my credentials. As soon as I try to run another query (which works in the browser, I might add) like https://${auths.discourse.domain}/admin/reports/signups.json, Pipedream throws back a 404 with the error The requested URL or resource could not be found.
I know the resource exists (I can paste the same URL into the browser and it works), so can you help me figure out why Pipedream can’t access these reports?
I was, but I had generated an API key for all users, and this morning when I tried generating one tied to my admin username things began working.
Maybe it’s worth noting that in the docs somewhere - or in the post about reverse-engineering undocumented API endpoints? I thought for sure I was doing something wrong by the end of yesterday, but I couldn’t see any mention in the docs of different permission levels for certain API routes versus others.
