HTTP

The HTTP output allows you to send features and other text to an HTTP endpoint via POST requests. A request will be sent for each output feature sent to the output.

Example

  • An analyst configures an HTTP output to send features in a custom JSON format to a designated webhook.

Usage notes

  • When sending JSON as a POST body, wrap the JSON with the Text() Arcade expression to properly format the JSON.
  • When using the HTTP output, it is important to understand the velocity of the data. Each record sent to the output will generate a separate request. This could quickly overload the capacity or rate limiting settings of a web server. The recommended best practice is to use the HTTP output for incidents expected to occur infrequently.

Parameters

ParameterDescriptionData Type

URL

The URL over which to send output requests.

String

POST body

An Arcade expression that will evaluate to the POST body being sent.

Arcade Expression

Content-Type

Sets the Content-Type header for outgoing requests.

  • Plain Text: text/plain
  • JSON: application/json
  • CSV: text/csv
  • XML: text/xml

String

URL Parameters

Optional URL parameters to be included in the URL of the HTTP request sent to the specified website.

While parameters can also be set in the URL parameter above, the URL parameters entered here as a separate property will override any matching parameter supplied in the URL parameter.

Parameters defined in this property will always be URL encoded.

Key-Value Pair

Custom headers

Optional custom headers to be included in the HTTP request sent to the specified website. For example, custom headers can be used to specify a third-party API key or authorization header.

Key-Value Pair

Considerations and limitations

  • The web server must be externally accessible on the Internet.