Webflow does not provide native functionality to authenticate HTTP GET requests without custom code. However, you can achieve this by utilizing third-party services or by integrating custom code into your Webflow project.
One approach is to use a service like Zapier or Integromat to handle the authentication process. These services allow you to create workflows or scenarios that can authenticate HTTP GET requests and trigger other actions based on certain conditions. You can integrate Webflow with Zapier or Integromat using Webflow's API. By setting up the authentication logic in these services, you can pass the authenticated data to your Webflow project.
Regarding your second question, Webflow's built-in Logic feature (previously called Collection Lists) enables you to create dynamic content based on server-side data. However, Logic in Webflow is limited to working with data from Webflow's own CMS. It cannot directly trigger server-side calls on page load or accept URL parameters.
To achieve server-side API calls and handle URL parameters, you would need to use custom code. You can embed JavaScript code directly in your Webflow project or utilize Webflow's HTML Embed element to inject custom code snippets. Within these custom code snippets, you can make use of JavaScript libraries or fetch functions to make server-side API calls and pass URL parameters.
Lastly, once you have received the data from your server-side API call, you can then use JavaScript to manipulate the HTML elements in your Webflow project and dynamically display the returned data. You can target HTML elements using their class names or IDs and update their content programmatically to reflect the data received from your server-side logic.
In summary, while Webflow offers its built-in Logic feature for working with its own CMS data, authentication of HTTP GET requests and server-side API calls typically require the use of third-party services or custom code integrations.