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 option is via HTTP POST requests made to a web server, in this case ArcGIS Velocity. The HTTP Receiver feed 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.
Example
- An organization has devices configured to push data to a specified Velocity HTTP endpoint via POST requests.
- A GIS analyst writes a python script that processes features and pushes data to a specified Velocity HTTP endpoint via POST request each time the script executes.
Usage notes
- HTTP POST requests should be sent as plain text.
- The HTTP Receiver feed is configured by the user including schema and key field specification. Once the feed is created, on the feed details page, the HTTP Endpoint Path is available. This is the URL to which data can be pushed via HTTP POST.
- Set authentication type to ArcGIS to utilize OAuth2.0 authentication. Each incoming message must then include a valid token for the owner of the feed. Messages without a valid token will be rejected.
- After configuring feed connection properties, see Configure input data to learn how to define the schema and the key properties.
Parameters
| Parameter | Explanation | Data Type |
|---|---|---|
HTTP Endpoint Path | The full URL over which to send messages. This parameter is generated and populated by Velocity after the feed is published. | String |
Authentication type | Whether incoming messages will be authenticated. Options are None and ArcGIS. If None is selected, no authentication is done. If ArcGIS is selected, each incoming message must include a valid token for the owner of this feed. Messages without a valid token will be rejected. The token must be in the request headers as: Authorization: Bearer <your token> | String |