It's indeed fixed by using our internal utility. Now I am hitting an error "Unexpected token < in JSON at position 0" This one trips up beginners, but as an experienced bug write, I know what it's all about: an API that should return JSON is instead returning HTML (an error or the wrong page)
0 likes 1 replies
?