Connector

Collect Stripe prices and products in AWS Athena

Keep Stripe products, prices and subscription items as tables that AWS Athena queries. A custom OWOX connector loads the catalogue and what customers actually subscribe to, so plan mix is a query away.

StripeConnectedBalance transact…ChargesCustomersDisputes
Data MartPublishedone definition
AWS AthenaIdAccou…Livem…Daily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Endpoints

Stripe Endpoints

Documentation

14 Stripe endpoints you can import. Each lands in its own table in your data warehouse.

S00 · Why

Why look at prices beside what customers actually buy

A price list says what you sell. Which plans customers pick, and which ones fade, is in the subscription items. Reading the catalogue against real subscriptions needs both in one data warehouse, joined on the price.

  • See which plans carry the subscriptions
  • Spot active prices nobody uses
  • Compare monthly and yearly plans in one query
StripeCatalogue, prices
OrdersStore sales
UsageProduct events
Your data warehouseAWS AthenaStripeOrdersUsageJoined by idPrice publishedPlan subscribedOne query shows which prices customers pick.

S01 · Step 1

Step 1: Connect Stripe and pick the fields

Create a Data Mart, choose Stripe as the data source and add a restricted API key with read access. Open an endpoint and tick only the fields you need.

  • Prices carries the product, currency, amount, billing scheme and interval
  • A custom connector: the restricted API key is yours
New Data MartChoose a sourceShopifyStripeGoogle AdsAuthorizeConnectedEndpointPricesBalance transacti…ChargesCustomers
Prices17 fieldsproductactivecurrencyunit_amounttyperecurring_interval

S02 · Step 2

Step 2: Load Stripe into AWS Athena

Each endpoint becomes its own table, and refresh settings are set in the Data Mart. Run it and the first load lands as a table in the database you choose in AWS Athena. The location is pre-filled from your data storage, and you can change it.

  • Products, prices and subscription items each get their own table
  • Every run is logged in Run History
DestinationAWS AthenaDatabasestripeTablepricesRun
Run HistoryPendingRunningSuccessIncremental load
Tablestripe.prices

S03 · Step 3

Step 3: Get a business-friendly Stripe output schema

After the first run you get the output schema: every field with its type and a description. unit_amount is in the smallest currency unit, and the schema says so.

  • recurring_interval says month, year, week or day for recurring prices
  • billing_scheme separates per-unit from tiered prices
stripe.pricesOutput schemaFieldDescriptionproductProduct id (prod_). Join to…activeWhether the price can be used…currencyThree-letter ISO currency code…unit_amountPrice per unit in the smallest…typeone_time or recurring.recurring_intervalmonth, year, week or day for…

S04 · Step 4

Step 4: Keep the Stripe tables linked

Products, prices and subscription items stay separate tables, joined by ids. Together they become the catalogue part of one Stripe data model.

  • Prices carry the product id; subscription items carry the price id
  • Add orders and product usage to the same model
Productsidnameactive
Pricesidproductunit_amount
Subscription itemsprice_idquantityrecurring_interv…

S05 · Step 5

Step 5: Schedule the Stripe refresh and backfill history

Set it once. A daily scheduled refresh reads new rows, and a manual backfill reloads the whole catalogue, which is how changes to an existing price arrive.

  • Daily runs with no pipeline to maintain
  • Backfill the full catalogue the first time you connect
ScheduleRun on a scheduleDaily 09:00
BackfillRun backfill
Run HistoryDaily scheduleManual backfillDaily schedule

S06 · Step 6

Step 6: Reuse the same Stripe table everywhere

One table feeds your data model, spreadsheets, dashboards, AI assistants and scheduled insights in Slack or email.

  • Define a plan once
  • Every report reads the same table
StripeData MartPublished
Your data model
Google Sheets
Data Studio dashboards
Claude, ChatGPT
Slack, email

Recent updates

Why OWOX

Why OWOX for Stripe in AWS Athena

The Stripe product catalogue is a settings page. OWOX makes it a set of tables in your own data warehouse that AWS Athena can query.

  • You own the data. It lands in your own data warehouse, in tables you control.
  • Catalogue and demand together. Prices join subscription items, so plan mix is measured.
  • Query it where you already do. AWS Athena reads the tables directly.
  • One place to fix. A Stripe API change is a new connector version, not a rewrite of your tables.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

176K Source: Internal OWOX data as of 2026-10-02

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

165K3

In Open Source We Trust

Customers