Examples of using Request payload in English and their translations into Spanish
{-}
-
Colloquial
-
Official
This mapping template generates the required integration request payload for the DescribeStream action of Kinesis from the method request's stream-name path parameter value.
no mapping is applied: the method request payload is passed through the integration request to the backend
For the POST method on an API resource, the method request payload can be passed through to the integration request without modification, if the method request's payload is of the same format as the integration request's payload.
the small HTTP request payload, and the reply bundles the SYN,
The mapping templates translate method request payloads to the corresponding integration request payloads and translate integration response bodies to the method response bodies.
Mapping templates for a request payload of specified MIME types.
This mapping template assumes that the method request payload is of the following format.
The applicable request payload adheres to the configured JSON schema request model of the method.
CONVERT_TO_BINARY: Converts a request payload from a base64-encoded string to a binary blob.
CONVERT_TO_TEXT: Converts a request payload from a binary blob to a base64-encoded string.
Specifies how a request payload of unmapped content type is passed through the integration request without modification.
We will define a mapping template to map the incoming path parameter values to the required integration request payload.
The following example sets mapping templates for a request payload of the application/json and application/xml MIME types.
We will enable a request validator to ensure that the client submitted the valid request payload before API Gateway call the Lambda function.
Choose Method Execution and then choose Integration Request to set up the mapping template to translate the client-supplied query strings to the integration request payload as required by the Calc function.
the backend requires that a binary request payload is passed in as a JSON property.
no mapping template is defined, you can choose to pass the client-supplied request payload through the integration request to the backend without transformation.
Set the contentHandling property of the Integration resource to CONVERT_TO_BINARY to have the request payload converted from a Base64-encoded string to its binary blob, or set the property to CONVERT_TO_TEXT to have the request payload converted from a binary blob to a Base64-encoded string.
The ListStreams request takes a payload of the following JSON format.
To define the method request payload, do the following.