SORACOMDataPost

Description

The SORACOM Data Post component allows sending data to SORACOM's Harvest.

actioncomponent-soracomdatapost

Preliminary Setup on SORACOM's Side

In SORACOM's management console, assign the target SIM card to a SIM group and enable Harvest Data in the settings.

※A SORACOM Air SIM card or SORACOM Arc is required to connect Gravio to the internet.
※For operations on SORACOM's management console, please contact SORACOM directly.

Content-Type Property for HTTP Request Body

Content-Type PropertyBody Content During HTTP Request
DefaultAutomatically selects the Content-Type based on the type of the input payload.
String typeExecutes the HTTP request with the Payload as a string using "text/plain; charset=utf-8".
JSON array, JSON objectExecutes the HTTP request with the Payload marshalled into a byte array as "application/json".
Byte arrayExecutes the HTTP request with the Payload converted to a string as "application/octet-stream".
OthersExecutes the HTTP request with the string-converted Payload as "text/plain".
application/x-www-form-urlencodedThe input payload is treated as a JSON object type, where key-value pairs are sandwiched by '=' and separated by '&', then sent in the body during the HTTP request. (An error occurs if the input is anything other than a JSON Object type).
multipart/form-dataThe input payload is treated as a JSON Object type, where key-value pairs are separated in multipart format, and the Content-Type of multipart/form-data is automatically appended with a boundary during the HTTP request. (An error occurs if the input is anything other than a JSON Object type).
Any other Content-Type entered manuallyOutputs the input payload converted to a byte array as specified by the entered Content-Type.

Input and Output Payload

Input PayloadDescription
cv.PayloadThe data to be sent. Please refer to the Harvest documentation for usable formats.
Output PayloadDescription
cv.PayloadIf the HTTP response's Content-Type header is "application/json", it is stored as a JSON type; if "text/*" and a charset (utf-8/shift_jis/euc-jp/iso-2022-jp) is specified, it is stored as a string; otherwise, it is stored as a byte array.

Component Properties

Property NameDescription
Content-TypeHTTP header's Content-Type
TimestampDate of the data *1
TimeoutHTTP request response timeout value

*1 Refer to the supported date formats below for the date formats supported.

Component Variables

Component VariableDescription
cv.PayloadBody of the response
cv.StatusCodeResult of the request
cv.HeadersResponse headers
cv.ContentLengthLength of the response

Supported Date Formats

Timestamp supports the following formats:
time.RFC3339 format
"2006-01-02T15:04:05.9999999Z"
"2006-01-02T15:04:05Z"
"2006-01-02 15:04:05.9999"
"2006-01-02 15:04:05"
"2006-01-02"