Rather than having an IoT system make requests for external data, a common workflow is to push data from devices within an organization's IoT infrastructure. One way is through HTTP POST requests made to a web server. The HTTP Receiver feed in ArcGIS Velocity creates a built-in HTTP endpoint that can be used to programmatically send data from IoT devices and applications to Velocity with HTTP POST requests.
Examples
The following are examples of using the HTTP Receiver feed:
- An organization has devices configured to push data to a specified Velocity HTTP endpoint using POST requests.
- A GIS analyst writes a Python script that processes features and pushes data to a specified Velocity HTTP endpoint using a POST request each time the script runs.
Usage notes
Keep the following in mind when working with the HTTP Receiver feed:
- Send HTTP POST requests as plain text.
- The HTTP Receiver feed is configured by you, including the schema and key fields. Once the feed is created, the URL is available on the feed details page under HTTP Endpoint Path. This is the URL to which data can be pushed using an HTTP POST request.
- Set the Authentication type parameter to ArcGIS to use open authorization (OAuth) 2.0 authentication. Each incoming message must include a valid token for the owner of the feed. Messages without a valid token are rejected.
- After configuring the feed connection parameters, refer to configuring input data to learn how to define the schema and the key fields.
Parameters
The following are the parameters for the HTTP Receiver feed:
| Parameter | Description | Data type |
|---|---|---|
HTTP Endpoint Path | The full URL to use to send messages. The URL is generated and populated by Velocity after the feed is started. | String |
Authentication type | Specifies the authentication type for incoming messages. Options are None, ArcGIS, and Basic. If None is specified, no authentication is performed. If ArcGIS is specified, each incoming message must include a valid token for the owner of the feed. Messages without a valid token are rejected. The token must be in the request headers as Authorization: Bearer <your token>. | String |
Additional logging | Specifies whether logging for raw HTTP requests and responses issued by Velocity is enabled. Note:Only enable this parameter for troubleshooting purposes and disable it when troubleshooting is complete. Once enabled, start the feed, and the debug level logs are available on the feed logs page. Contact Esri Technical Support for assistance if necessary. | Boolean |
Username | Specifies the username to access HTTP Receiver. This parameter is available when the Authentication type value is set to Basic. | String |
Password | Specifies the password to access HTTP Receiver. This parameter is available when the Authentication type value is set to Basic. | String |
Considerations and limitations
HTTP Receiver feeds with the ArcGIS authentication type can be shared with write privileges to other users and groups. When an HTTP Receiver feed is shared with write privileges, users and groups who it is shared with can write data to the feed. Do not share a feed with write privileges enabled if you do not want other users and groups to write data to it. You can enable and disable write privileges from the feed details page in Velocity.