FlyETL
Log inStart free

For small SaaS and internal tool teams

Prepare database and internal API datafor your application to read

Your app needs prepared customer, order, or business data, but you are still maintaining extraction and cleanup scripts. Build a visual pipeline, then let your app read the successful result through a Query API.

Start freeGet help connecting

Free includes visual processing and the Query API, within plan limits. View setup steps

  1. 01

    Connect data

    Databases / HTTP APIs

    • PostgreSQL
    • MySQL
    • Internal HTTP APIs
  2. 02

    Prepare and run

    Visual data pipelines

    • Filters and joins
    • Field processing
    • Publish and run
  3. 03

    Read from your app

    Datasets / Query API

    • Read-only JSON
    • Field selection
    • Cursor pagination

Start with one recurring task

Are these scripts taking up your time?

01

Combining data repeatedly

Customer records live in a database and extra details in an internal API. Every refresh means fetching data and aligning fields again.

02

Rules buried in code

Filters, joins, and field transformations are scattered across scripts. A business rule change needs another code change.

03

Maintaining a delivery API too

Once the data is ready, you still need to serve it to your app and preserve usable results when a refresh fails.

Clear preparation and predictable reads

Put the rules on a canvas. Read the successful result.

  • Check before delivery

    Connect data and configure filters, joins, and field processing. Preview a sample, then publish and run to produce an output dataset.

  • Read from a stable address

    Enable the Query API on the dataset and choose allowed return and filter fields. Your app reads with an endpoint API key; refreshes keep the same address.

  • Keep the last successful result

    A later run updates current content only after it succeeds in full. Failure or cancellation leaves the previous successful result available.

How your application reads

HTTP request

GET /api/v1/published-datasets/{endpointId}?limit=100&field=customer_id&field=plan
Authorization: Bearer {queryApiKey}

JSON response

{
  "data": [
    {
      "customer_id": "c_001",
      "plan": "pro"
    }
  ],
  "nextCursor": null,
  "metadata": {
    "contentUpdatedAt": "2026-10-01T08:00:00Z",
    "datasetRowCount": 1,
    "returnedRows": 1
  }
}
Request and response show the structure only. Use the endpoint, key, fields, and update time from your dataset.

Refresh with a run. Read when needed.

The Query API reads the latest successful result without triggering computation. Full runs refresh the data; scheduled refreshes depend on your plan. This suits application data that can update in batches. It does not provide real-time CDC synchronization or a write API.

See plans and refresh limits

Start with a real task

Choose the data your application is waiting for

Sign up and build your pipeline, or tell us your data sources, expected fields, refresh frequency, and application use so we can help assess the connection.
Start freeGet help connecting

Email support@flyetl.com with your requirements. You do not need to send connection credentials or API keys.