|status||The status code that API Gateway uses to map the integration response to a MethodResponse status code.|
|content||Specifies how to handle request payload content type conversions.|
|response||The response parameters from the backend response that API Gateway sends to the method response.|
|response||The templates that are used to transform the integration response body.|
|selection||Specifies the regular expression (regex) pattern used to choose an integration response based on the response from the back end.|
The status code that API Gateway uses to map the integration response to a MethodResponse status code.
(optional, default: none the request payload is passed through from the method
request to the integration request without modification.)
Specifies how to handle request payload content type conversions.
The response parameters from the backend response that API Gateway sends to the method response.
Use the destination as the key and the source as the value:
- The destination must be an existing response parameter in the MethodResponse property.
- The source must be an existing method request parameter or a static value. You must enclose static values in single quotation marks and pre-encode these values based on the destination specified in the request.
The templates that are used to transform the integration response body.
Specify templates as key-value pairs, with a content type as the key and a template as the value.
Specifies the regular expression (regex) pattern used to choose an integration response based on the response from the back end.
For example, if the success response returns nothing and the error response returns some string, you
could use the
.+ regex to match error response. However, make sure that the error response does not contain any
\n) character in such cases. If the back end is an AWS Lambda function, the AWS Lambda function error
header is matched. For all other HTTP and AWS back ends, the HTTP status code is matched.