Edit

Share via

Add HTTP source to an eventstream (preview)

This article shows you how to add an HTTP source to an eventstream.

The HTTP connector provides a no-code, configurable way to stream data from any REST API directly into Eventstream for real-time processing. It allows you to continuously pull data from SaaS platforms and public data feeds and automatically parse JSON responses into structured events. It also offers example public feeds to help you get started quickly—simply select an example API, enter your API key, and let Eventstream prefill the required headers and parameters.

Prerequisites

  • Access to a workspace in the Fabric capacity license mode (or) the Trial license mode with Contributor or higher permissions.
  • If you don't have an eventstream, create an eventstream.

Add HTTP as a source

If you haven't added any source to your eventstream yet, select the Use external source tile.

Screenshot that shows the selection of the tile for using an external source.

If you're adding the source to an already published eventstream, switch to Edit mode. On the ribbon, select Add source > External sources.

Screenshot that shows selections for adding external sources.

Search for http, and select Connect to add the HTTP connector to your eventstream.

Screenshot that shows the selection of HTTP as the source type in the Select a data source wizard.

Configure and connect to HTTP

  1. In the wizard, you can select one of the Example public APIs to get started quickly with predefined headers and parameters, or select Exit to configure your own HTTP connector.

  2. Here are the example public APIs you can use to quickly get started with the HTTP connector:

    • Binance — Get the latest Bitcoin price
    • CoinGecko — Get the current Bitcoin price in USD
    • Transport for London — Get live arrival predictions for a London station
    • Alpha Vantage — Get the real-time MSFT stock price
    • OpenWeather — Get the weather forecast for a location
    • NewsAPI — Get the latest business headlines in the US

    Screenshot that shows example API page.

  3. Alternatively, select Exit to skip the example and configure your own HTTP connection without an example.

    Screenshot that shows go without example API.

  4. If you select an example API, choose whether eventstream automatically creates the connection before Apply example:

    • Create a new connection for me: Automatically creates the connection and prefills the required HTTP headers and parameters.
    • If this option is selected, you need to enter your API key to create connection, except when using Binance, which doesn’t require an API key.
    • If you select Use existing connection, only the headers and parameters are prefilled, and you need to create the connection manually.

    Screenshot that shows creating a new connection for me option.

  5. If you’re creating the connection manually or configuring your own HTTP source without an example, select New connection and provide the following details:

    • Base Url: Base Url of Http Endpoint. Information will be sent to the URL specified. Ensure you trust the URL entered.
    • Token Audience Uri: The resource that the token is intended for, e.g, https://vault.azure.net, for connecting to Azure keyvault endpoint.
    • Connection name: Enter a name for the connection.
    • Authentication kind: Choose from Anonymous, Basic, API Key, Organizational account, or Service principal.

    Screenshot that shows the new connection page.

  6. Request method: Select GET or POST.

  7. Headers and Parameters: Configure as needed.

  8. Request interval (s): Specifies the time in seconds to wait between consecutive requests; valid range is [1, 3600].

  9. You may expand Advanced settings to access more configuration options for the HTTP source:

    • Maximum retries： The maximum number of times the connector retries a request when an error occurs; valid range is [10, 100].
    • Retry backoff (s)： The time in seconds to wait following an error before the connector retries; valid range [1, 3600].
    • Retry status code： The HTTP error codes returned that prompt the connector to retry the request. Enter a comma- separated list of codes or range of codes. Ranges are specified with a start and optional end code. For example:
      • 400- includes all codes greater than or equal to 400 and
      • 400-500 includes codes from 400 to 500, including 500.
      • 404,408,500- prompts the connector to retry on 404 NOT FOUND, 408 REQUEST TIMEOUT, and all 5xx error codes. Some status codes are always retried, such as unauthorized, timeouts, and too many requests.

  10. You can edit the HTTP source name by selecting the Pencil icon for Source name in the Stream details section. Then select Next.

    Screenshot that shows the configured settings.

  11. On the Review + connect page, review the configuration summary for the HTTP source, and select Add to complete the setup.

    Screenshot that shows the review configuration page.

You can see the HTTP source added to your eventstream in Edit mode.

A screenshot of the added HTTP source in Edit mode with the Publish button highlighted.

Select Publish to publish the changes and begin streaming data from HTTP source to the eventstream.

A screenshot of the added HTTP source in Live view with the Publish button highlighted.

Limitation

  • The HTTP source currently doesn't support CI/CD features, including Git Integration and Deployment Pipeline. Attempting to export or import an Eventstream item with this source to a Git repository may result in errors.

Related content

Other connectors:

  • Last updated on