Thanks for getting back to me. I’ve had a full dig into what’s going on now and can replicate the issue locally with a dev account.
It looks like our code is failing with any communication to Freeagent’s API - it just showed up as the PDF endpoint as that’s all we use the API for at this time (as well as negotiating new access tokens).
So I’m looking at a test we’ve got set up in the library which reproduces the issue. From the API we get a
200 response but the content is bonkers:
Now to me, that looks like we’re trying to read a HTTPS response as HTTP and not decrypting the TLS response, but we’re using Refit and .NET core in this library which will be doing all that for us. I can’t prove that’s the issue though.
Is there any way you can tie logs up at your end with these requests (what info do you need from me to do that? Our app is called: “Timetastic test freeagent app” that I’ve been testing with this morning) Or do you know if there have been any changes to SSL termination, authentication or the like on December 2nd as that’s when our logs first started reporting errors (just after midnight).