Looking at the API, they require the use of unusual headers, plus base64 encoding of the content. They also require you to make a signature using HMAC, which we can't do in the Qlik Sense connectors.
If you're still looking, and you're on Qlik Cloud, it's possible that the headers could be prepared with a custom code block in Application Automation, and the data saved to the tenant for loading into an app.
Looking at the API, they require the use of unusual headers, plus base64 encoding of the content. They also require you to make a signature using HMAC, which we can't do in the Qlik Sense connectors.
If you're still looking, and you're on Qlik Cloud, it's possible that the headers could be prepared with a custom code block in Application Automation, and the data saved to the tenant for loading into an app.
Thanks Dave... not done anything yet as still waiting for customer to sign off the project. I could tell it was a pretty old API, but you've confirmed that we probably should be looking for a different one 🐵 There are other ones out there - the customer came up with that one!
