Hey folks, can I use application/json as Content-Type when updating a post via the API? The docs say I can, but I am starting to think I cannot .. I constantly get ["BAD CSRF"] and I have no clue what that means. If I need to use multipart/form-data do you folks have any pointers on how I build my…

[Bild] pedroleaoc: When I edit the post via the GUI, there seems to be a PUT request to the topic’s URL (apart from the one that actually edits the post posts/post_id.json ) which I can’t reproduce with a limited API key, only the global. I don’t see why, however, I wouldn’t be able to edit the …

[Bild] pedroleaoc: header = CaseInsensitiveDict() header["Authorization"] = '{"api-key": "longapikey", "api-username": "myusername"}' You need to send the Api-Key and Api-Username as their own headers, not in the Authorization header. Something like this should work better: header = CaseInse…

Thanks for your reply, David. That’s super weird, when I format the header the way you showed, I get: {"errors":["You are not permitted to view the requested resource. The API username or key is invalid."],"error_type":"invalid_access"} If I add the ["Authorization"], it works. That’s for a simp…

[Bild] pedroleaoc: That’s for a simple GET request, I still can’t do the PUT . Likely something is malformed with your PUT request then if GET is working when you are doing it the wrong way with the Authorization header. It is working because you don’t have to be authorized at all the make th…

@pedroleaoc here is a little sample python script that demonstrates how to make authenticated requests and how to send the request data for put/post requests. # discourse-api-demo.py import requests from requests.structures import CaseInsensitiveDict # Basic GET request to a public url, no headers…

Doh, of course! Not all GETs require Authorization! That’s such a nice pointer, I will look into that. Thanks! Things that I already know by reverse engineering: api-key rather than api_key The PUT request requires "content-type": "application/x-www-form-urlencoded" The data is not in JSON (it’s…

[Bild] pedroleaoc: The PUT request requires "content-type": "application/x-www-form-urlencoded" The data is not in JSON (it’s encoded, although I don’t seem to find the right encoding) Please see my post just above this. You can use the json=data instead of the data=data format in your reque…

Awesome, I am now able to edit my post! Thanks for your help! There’s only one more issue, the key I am using is global. When I try with a key with write and read permissions only, I get: You are not permitted to view the requested resource. The API username or key is invalid.. When I edit the post…

No! I don’t even have that option! Will look into that, thanks for the help once again. [image]

Was ist der korrekte `content-type` beim Bearbeiten von Beiträgen?

Entwickler

david (David Taylor) 10. August 2021 um 10:12 2

Sie müssen den Api-Key und den Api-Username als eigene Header senden, nicht im Authorization-Header. Etwas wie dies sollte besser funktionieren:

header = CaseInsensitiveDict()
header["Api-Key"] = 'longapikey'
header["Api-Username"] = 'myusername'

Dies scheint das gleiche Problem wie in Ihrem vorherigen Thema zu sein:

Thema		Antworten	Aufrufe
Getting ["BAD CSRF"] when updating topic via API [python] Development rest-api	2	1046	9. August 2021
"BAD CSRF" when executing PUT using API, curl, and PHP Development rest-api	5	2407	5. Oktober 2021
Need Help updating profile info via API Development rest-api	6	538	4. Mai 2024
I'm getting bad CSRF error even after setting api keys and usernames to my headers General	2	903	16. April 2022
Creating a topic via the API using Node.js Development	12	2304	30. März 2020

Was ist der korrekte `content-type` beim Bearbeiten von Beiträgen?

Verwandte Themen