WilliamNadeau's account

Yes. I can receive successful responses, which means that the API key must be valid and the URI correct. It's just that the first call always fails. This would be a problem that I could work around by keeping HttpClient alive for the whole application lifecycle and automatically retrying 401's, but I was hoping to be able to use the SDK, and the way SDK works it causes it to fail every request. I would rather not have to roll my own REST client nor modify the SDK code to get it working (if I can avoid those options).

I'm using the .NET SDK version 11.13. I have only connected to sandbox and I'm only working with a development account so far. I'm on a corporate network so I don't have access to the proxy. I haven't attempted to use it outside of the corporate network yet, I'll give that a try tonight and see if can connect clean.

I did, and I was able to get through with no issues.

I did try both of the suggestions, configuring the client with the proxy information as well as setting the default proxy credentials, both seem to fail. At this point I believe that the issue is on our side, probably with configuration of the proxy. I'll continue to investigate on my own and post back if I find evidence to the contrary. Thanks for your assistance!

Sorry for the delay. We discovered that the issue is on our side, though we haven't fixed it yet. I appreciate the help and the follow-up, though. Thank you.