A company has a serverless application that uses Amazon API Gateway backed by AWS Lambda proxy integration. The company is developing several backend APIs. The company needs a landing page to provide

Setting the integration request Content-Type to text/html is incorrect; the mock integration request must use application/json because the mock endpoint communicates in JSON internally.

Configuring only the integration request with application/json without properly setting the response mapping and Content-Type for the HTML output will not produce a renderable HTML page for the client.

In a mock integration, the integration request mapping template uses Content-Type application/json to define the static JSON payload returned by the mock, and the integration response mapping template transforms that payload and sets the Content-Type to application/json in the request body while the method response header returns text/html, enabling the browser to render the HTML landing page correctly.

Setting the integration request Content-Type to text/html is not valid for mock integrations, which require application/json in the request mapping template to define the statusCode and body for the mock response.