Ahmad Nassri

the current version does not support oAuth 2.0 authentication flow, though it can still make calls if you manually input keys and tokens. full oAuth 2.0 flow will be supported...

I can see where it can be confusing ... the next version (work in progress) has an enhanced interface so it should make things a "little bit" clearer ... but...

Good catch, I didn't do much validation in version, will add to the next.

yep, that's no good, I think I came across that and fixed it in the development branch, I'm a few days away from releasing the new version which will include...

sounds like it ... I'll investigate.

interesting, I've gotten that a couple of times but I wasn't able to determine what was the cause, thanks for the details, I will fix ASAP.

hmm, thanks, I'll look into it ... wondering if it's something to do with with the response body or the headers ...

not sure what you mean by that exactly? you want to be able to make API calls and get the result as a file?

@ShawnTuatara you are correct, this was ignored when I first built the feature, as it wasn't something a lot of people used... but it is needed, and will be added...

There is no reason why you can't do that? I use it all the time! Was there any specific error message you are getting when trying to set the header?