Docs / Data sources / ReBound Returns

ReBound Returns

Ecommerce

Built when you ask for it

Sync ReBound Returns return, order, refund, and warehouse 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 ReBound Returns connector syncs your ecommerce returns management data into analytics-ready tables in your data warehouse. Pull returns, orders, refunds, and warehouses from the ReBound Returns 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:

  • Returns
  • Orders
  • Refunds
  • Warehouses

How it gets built

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

What you will need

OAuth 2.0. Not self-serve: your ReBound Implementation Manager issues the Client ID, Client Secret, and Flow Key during store setup.

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 ReBound Returns connector?
Not as a finished connector yet. Ingest builds it from ReBound Returns's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can ReBound Returns 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.

ReBound Returns API documentation: https://docs.reboundreturns.com/docs/introduction

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 ReBound Returns