Docs / Data sources / Heartland Retail

Heartland Retail

Ecommerce

Built when you ask for it

Sync Heartland Retail sale, item, customer, and location data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Heartland Retail connector syncs your point-of-sale data into analytics-ready tables in your data warehouse. Pull sales, items, customers, and locations from the Heartland Retail API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Sales
  • Items
  • Customers
  • Locations

How it gets built

  1. Choose Heartland Retail when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Heartland Retail's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Heartland Retail itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API token (Bearer). Generate one from your account page under the API section; new OAuth 2.0 app registrations are currently closed, so token auth is the only self-serve path today.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Heartland Retail connector?
Not as a finished connector yet. Ingest builds it from Heartland Retail's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Heartland Retail data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Heartland Retail API documentation: https://dev.retail.heartland.us

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for ecommerce teams: Shopify, Etsy, Faire, Walmart Marketplace, Walmart Connect, Mercado Libre.

Request Heartland Retail