I have a very simple function that “should” work but it is not for some reason. Can someone help me understand what we are doing wrong. We keep getting the “BAD CSRF” error. public function changeName() { $url = 'https://www.website.com/{username}.json'; $data = ['name'=>'James', 'api_key'=>DISCOURSE_API, 'api_username'=>'system']; $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "PUT"); curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type:multipart/form-data')); curl_setopt($ch, CURLOPT_POSTFIELDS,http_build_query($data)); echo $response = curl_exec($ch); if (!$response) { return false; } } By the way I already tried moving the api_key and api_username to the URL above as GET but no difference.

You need to put the Api-Key and Api-Username values in the request header. There’s a curl example near the end of this topic that could be helpful: Sync DiscourseConnect user data with the sync_sso route.

Thanks a lot! That did the trick. For anyone else with the same problem: $url = 'https://www.website.com/{username}.json'; $data = ['name'=>'George']; $api_key = CUSTOM_DISCOURSE_API; $headers = array("Content-Type: multipart/form-data;","Api-Key: $api_key","Api-Username: system",); $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "PUT"); curl_setopt($ch, CURLOPT_HTTPHEADER, $headers ); curl_setopt($ch, CURLOPT_POSTFIELDS,http_build_query($data)); $result = curl_exec( $ch ); if ( curl_errno( $ch ) !== 0 ) { // Handle error, call curl_close( $ch ) and return. } curl_close( $ch ); $discourse_user = json_decode( $result );

Just to add to that, if someone needs to update a “user_field” replace the $data with this: $data = ['user_fields' => ['1' => 'Something']]; The number “1” being the first user_field I created (as they are assigned by number not name).

[תמונה] brospars: Since when it’s mandatory ? Didn’t find it in the changelog. I made a tool 2-3 years ago [תמונה]Discourse REST API Documentation :warning: Deprecation Warning! On April 6th, 2020 we dropped support for all non-HTTP header based authentication (excluding some rss, mail-receiver, and ics routes). This means that API requests that have an api_key and api_username in the query params or in the HTTP body of the request will soon stop working. Sorry about any issues this caused, we did do a slow roll out of this change and notified people the best we could, but its hard to catch every deprecation use.

"שגיאה BAD CSRF" בעת ביצוע PUT באמצעות API, curl ו-PHP

מפתח

brospars (Benoit Rospars) 5 באוקטובר,‏ 2021,‏ 9:32am 5

Since when it’s mandatory ?
Didn’t find it in the changelog. I made a tool 2-3 years ago to create categories in batch that worked perfectly fine and now I get this error…

נושא		תגובות	צפיות
Need Help updating profile info via API Development rest-api	6	675	4 במאי,‏ 2024
'BAD CSRF' while creating a new post Product Support	1	1943	23 באפריל,‏ 2020
Getting ["BAD CSRF"] when updating topic via API [python] Development rest-api	2	1121	9 באוגוסט,‏ 2021
Work Around to posting SSO	3	2585	18 במאי,‏ 2016
Can't verify CSRF token authenticity while creating topics Development rest-api	1	1255	4 בנובמבר,‏ 2022

"שגיאה BAD CSRF" בעת ביצוע PUT באמצעות API, curl ו-PHP

נושאים קשורים