Type of Data

Custom Data Feed


The HTTP GET data feed pulls content from a customer supplied URL and makes this data available to the Openmix application.

The customer’s data can be in any format - text, xml, JSON, html, csv, and so on Fusion does a simple pass through of the data from the customer’s endpoint to Openmix. The Openmix app is responsible for parsing the data and applying any desired rules for DNS/HTTP routing.

The customer’s data feed must be under 10K in size or Fusion will reject it. This is a hard limit imposed by the infrastructure app servers. The HTTP GET Fusion data feed also provides optional OAuth2 integration.

Set up in Fusion

You can access Fusion Data Feeds from the left navigation pane, under Openmix. For initial steps please refer to the Fusion Integration Documentation.

When you get to the service-specific configuration dialog box, enter the following:

  • Name: The name given to the data feed. This defaults to “Service - Platform Name” if not specified.
  • Run Every: The frequency with which the data feed is updated from the service.
  • Platform: The Platform that is associated with the data feed.
  • URL: The URL is an endpoint on the customer’s network that returns some data that the customer wants to see in Openmix.

Optional OAuth2 Configuration

A JSON payload with the following fields will be sent.

  • The optional OAuth2 configuration was originally designed to pull Openmix and Radar data via the ITM API.
  • Use the following technical implementation:
    • Before calling the customer’s desired (target endpoint, first obtain an OAuth2 request token
    • The OAuth2 token is requested via the customer’s token endpoint.
  • In the OAuth2 token POST request which must be HTTPS, the following request body is passed to the customer’s token generator:
    • client_id (user input on second HTTP GET config screen)
    • client_secret (user input on second HTTP GET config screen)
    • grant_type, hard-coded to “client_credentials”
  • An OAuth2 token is returned for subsequent API requests.
  • With a valid OAuth2 token, the customer’s target URL is called passing in the ‘Authorization: Bearer {token}’ request header
  • The good news for the HTTP GET OAuth implementation is that if you are calling an API endpoint (that is, Openmix or Radar), the OAuth2 configuration fields are not required. Fusion already knows the user’s OAuth2 client credentials and therefore passes them automatically for all ITM based API URLs.

Once the installation is complete, it is listed on the Fusion data feeds home page with a green status and monitoring metrics in the log history.

To edit a Fusion data feed click the data feed in the list and then click the Edit button. Once you have changed the configuration, click Save. This brings you back to the data feed list with your changes saved and applied to the data feed.