Ah, thanks. Setting OptionCustomRequest after OptionPostFields made all the difference.
Best, Max > Am 22.01.2020 um 16:11 schrieb Christian Schmitz > <supp...@monkeybreadsoftware.de>: > > > >> Am 21.01.2020 um 09:03 schrieb Maximilian Tyrtania <li...@contactking.de>: >> >> Let me rephrase my question: How would I have to set up my call so that it >> mimicks the successful terminal call >> >> curl --request PATCH \ > > -> OptionCustomRequest > >> | => --url https://api.zoom.us/v2/users/someUserID \ > > -> OptionURL > >> | => --header 'authorization: Bearer MyJWT...' \ >> | => --header 'content-type: application/json' \ > > -> SetOptionHTTPHeader with both in an array. > >> | => --data >> '{"first_name":"Test","last_name":"Coach","type":"1","job_title":"string","company":"SomeCompany","location":"Berlin"}' > > -> OptionPostFields > > > You may need to set OptionPostFields first and then OptionCustomRequest as > setting post fields may switch to POST request. > > Sincerely > Christian > > -- > Read our blog about news on our plugins: > > http://www.mbsplugins.de/ > > > > _______________________________________________ > mbsplugins@monkeybreadsoftware.info mailing list > %(list_address)s > https://ml-cgn08.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info Maximilian Tyrtania http://www.contactking.de _______________________________________________ mbsplugins@monkeybreadsoftware.info mailing list %(list_address)s https://ml-cgn08.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
