I want to fetch all topics by tag. I am sending a GET request to the URL https://discourse-url/tag/kind:feature.json. But I am getting the error "You are not permitted to view the requested resource. The API username or key is invalid.". Whereas my API-key and API-username are correct. What could be…

Just to confirm, you can use the same header to request, say /admin/users.json? (I think that’s an admin route, but you can check in a web browser)

Getting 404 error for this url. I can fetch any topic by sending the request to /t/topic-id.json but not able to do any other GET query successfully. What could be the possible problem

Can you get http://example.com/admin/dashboard.json? I’m sure that URL should work.

Not able to get it. Same error 404.

Then you’re not passing the credentials correctly. You can search for examples of how to pass them in the header. But I just tested this one: DISCOURSE_API_KEY==API_KEY= DISCOURSE_API_USER==API_USER= curl -s -X GET --header "Api-Key: $DISCOURSE_API_KEY" --header "Api-Username: $DISCOURSE_A…

I am passing credentials correctly. I verified it by trying to fetch an internal topic by id which can’t be fetched without proper credentials. But seems like only working query I can do is on discourse-url/t/tid.json. Anything else simply returns error 403.

Ungültiger Zugriff-Fehler

Produktunterstützung

Minhaj (Minhaj Shakeel) 10. Januar 2021 um 19:36 3

Fehler 404 für diese URL. Ich kann jedes Thema abrufen, indem ich eine Anfrage an /t/topic-id.json sende, aber keine andere GET-Abfrage erfolgreich ausführen. Was könnte das Problem sein?

Thema		Antworten	Aufrufe
Discourse API - Unable to query certain endpoints Product Support	7	1640	1. Oktober 2019
Access via Discourse API, key and/or user rejected Development rest-api	2	966	1. Dezember 2023
API Error: You are not permitted to view the requested resource Development rest-api	13	10659	19. Juni 2020
Discourse_api URL not found error Development rest-api	4	1479	23. Oktober 2020
New to API, 403 Errors Development rest-api	12	3638	11. August 2017

Ungültiger Zugriff-Fehler

Verwandte Themen