Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.

Flow on Helios XL Ingest API

On this page

Note

This is a Preview feature.

XL Ingest handles the initial transfer of large tables by breaking them into smaller logical partitions. You can use this API to select and configure tables for slicing, and transfer data from source databases to SingleStore in parallel slices.

Prerequisites

Before using the XL Ingest APIs, ensure that the table to be ingested is selected in Ingest, Skip Initial Extract is enabled for the table, and a full extract has been performed to copy only the schema.

Authentication

All requests must include authentication credentials. Refer to Flow on Helios API Authentication for more information.

Base URL

All XL Ingest API requests must be sent to the following base URL:

https://<flow-endpoint>:30084/ixl

Where <flow-endpoint> corresponds to the endpoint link for the Helios Flow deployment in Admin Portal > Organizations > Deployments > Flow > Endpoint (e.g.,  svc-abc123-flow.aws-virginia-8.svc.singlestore.com). To copy the endpoint, right-click the Endpoint link and select "Copy Link Address."

Flow on Helios XL Ingest API Reference

The following endpoints include HTTP methods, required headers, request and response formats, and example requests.

Last modified: January 30, 2026

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In