Dear VMoraal, I think it is time for you to pack your bag and start your weekend... You clearly can't read. The problem was due to the lack of declaration of the content-type in the request name. Somehow my brain was stuck somewhere else.   Other users beware! If you don't declare the content type, ESP will read the response of your request as HTML. <request name="api_query" contentType="application/json"> ... View more

Hi AndyT, Thanks for your answer 🙂 I'm currently on SAS Viya 2023.08 (v7.40.19), but...   Since posting my question, I have found that using a Basic HTTP authorization should theoretically work as I was able to successfully query the API with a curl command inside the pod where the ESP engine lives. While I couldn't find it in the documentation (I may not have been very thorough), The same Auth token can be used as an HTTP header. As a result, the previously mentioned login method is no longer necessary.   Maybe it would be an idea to include this sort of information in the documentation page for the URL connector?   My config file now looks like the one presented here: <url-connector> <url-publishers> <url-publisher name='myconnector'> <requests> <request name="myconnector"> <url><![CDATA[https://api-url.tld/api/resource/]]></url> <headers> <header name="Authorization">Basic [insert-key-here]</header> </headers> </request> </requests> <generate>0</generate> <opcode>upsert</opcode> <event-loops> <event-loop-json name='loop'> <use-json>#_content</use-json> <json>$.index</json> <function-context> <functions> <function name='example'>json(#_context,'volume1.data')</function> </functions> </function-context> </event-loop-json> </event-loops> </url-publisher> </url-publishers> </url-connector> Hope someone with the same problem will have found this useful. ... View more