Apologies for delayed response. That is a weird issue 
Is there a reason you use the V1 instead of the V3 api?
Not saying that the v1 should be exhibiting this behavior, but was wondering if you could give that v3 endpoint a go and see if it persists