I have created a TYK API end-point using TYK cloud. I want my TYK end-point to request data from a non-TYK API end-point which requires an authorisation token.
I have defined the non-TYK API end-point in the “Target Url” form in the “API designer” section. I thought that the authorisation data for the non-TYK API end-point could be included as payload somewhere in the TYK API end-point definition - e.g. from somewhere like in the “Advanced Options” within the “API designer” but doesn’t seem to be the case.
Is the above possible or does TYK cloud assume that target API URLs are only open?