This API accepts apikey in header to give more information on dataResource connection details.
But you can try the same API with apikey as a query param which gives you same information.
so i believe we might need to address this issue (using apikey as a query param and how we can use JWT instead of apikeys) if we want to completely decommission the apikeys.
This API accepts apikey in header to give more information on dataResource connection details. But you can try the same API with apikey as a query param which gives you same information. so i believe we might need to address this issue (using apikey as a query param and how we can use JWT instead of apikeys) if we want to completely decommission the apikeys.