Has something changed with the certificate/security on the API?

I’ve started to get errors when sending requests to the API despite the fact that it’s code that worked fine a couple of weeks ago. Also, I’m sending requests to the Document API using code that is identical except for the URL and that is working without error.

The error I’m getting is a fairly generic .NET one: “Authentication failed because the remote party has closed the transport stream” and research suggests it’s something to do with security on the HTTPS request. I’ve tried a few things but haven’t be able to figure it out and was wondering if anything had changed or anyone else is having problems.

Apologies for the slow response on this. Could you provide some further details. Is it all API end points or specific ones?

Sorry, I should have updated this thread as the problem has been resolved off-forums.

For the record it was a setting that had been changed on the secure certificate that rendered the API unusable in some older Windows environments. This has been updated and we’re all good now!