The discussion revolves around using the Discourse REST API for generating weekly statistic reports, particularly on try.discourse.org. orli wants to start early without admin keys and asks about access to try.discourse.org. itsbhanusharma suggests setting up a local development instance, noting it includes default seeded data itsbhanusharma. Falco clarifies that public data on try.discourse.org can be accessed without API keys, providing examples for fetching group and member data Falco. The conversation also covers the difference between API username and API key, with Canapin explaining that the username defines capabilities and the key acts as a password. Tarun_Sharma seeks clarification on whether each user needs their own API credentials, and Lilly directs him to the API documentation. Tarun_Sharma reports an error with an
Hi, I would like to create some weekly statistic reports using the REST API. I will be doing this for
forum linkingyourthinking com
but I would like to start early before I have gotten the keys from the administrator which might take a while, since they are in the middle of a 6 week workshop.
So I was hoping to begin right now with try.discourse.org, Is that possible? I have tried curl -X GET https://try.discourse.org/site.json
and it works nicely.
The api username will tell Discourse which capabilities are enabled. An admin or a regular user don’t have the same capabilities, and using one or another will restrict what you can achieve using the api.
the api key is the password to be used with the api username.
So in my scenario I only want to use the discourse api and my confusion is that every user who is using my app can create post, like, comment other features so now do i want to create api-username and api-key for each user to use respective api’s?