The following table indicates the supported input parameter mappings between HTTP request elements and ABL data types. Y and N indicate whether a mapping is supported or not. Assume any mapping not mentioned in these tables is not supported.

Table 1. Supported mappings between HTTP request elements and ABL data types (input)
ABL Data Types HTTP Request Elements
Path Query Form 1 Header Cookie Body Full URL
CHARACTER Y Y Y Y Y Y Y
LONGCHAR Y Y Y Y Y Y Y
INTEGER Y Y Y Y Y N N
DECIMAL Y Y Y Y Y N N
DATE Y Y Y Y Y N N
DATETIME Y Y Y Y Y N N
DATETIME-TZ Y Y Y Y Y N N
INT64 Y Y Y Y Y N N
LOGICAL Y Y Y Y Y N N
MEMPTR2 N N N N N Y N
ROWID Y Y Y Y Y N N
TABLE N N N N N Y N
DATASET N N N N N Y N
Note: ABL arrays (ABL variables defined with the EXTENT option) are encoded as JSON objects. see JSON input and output message formats for more information.
1 You can map individual form fields to input parameters if the request is a POST with standard form fields.
2 Mapping supported as Base64 encoded strings.