Integrations
Where your revenue data comes from
Every source Bastle can read, with its real status on the tile. A connector that is not built yet says so.
What does Bastle integrate with?
Bastle reads subscription and payment data from billing platforms, payment processors, accounting ledgers and app stores, backfills the history each source will serve, then keeps current over webhooks. 13 of the 13 connectors listed here can be connected today; the rest are marked Roadmap and are not available. Ingestion is read-only — Bastle never charges a card, retries a payment or changes a subscription upstream — and every connector is included free while Bastle is in beta.
- Live
- Ships today. Connect it from workspace settings and Bastle backfills the history it can reach.
- Beta
- Connectable today, with edge cases still being closed. Expect to check the first month's numbers against the source.
- Roadmap
- Not built. Cannot be connected, and nothing on this site should suggest otherwise.
4 sources
Billing platforms
Subscription billing systems hold plans, subscriptions and their whole history of upgrades, downgrades and cancellations. These are the sources that produce a complete metric set rather than a revenue total.
Stripe
BetaThe Stripe integration turns a Stripe account into Bastle's subscription data model: prices become plans, subscriptions carry their add-ons and discounts, and charges carry the Stripe fee from the balance transaction. Ongoing changes arrive over a signature-verified webhook endpoint within seconds of happening in Stripe, so MRR, churn and failed-payment state track the billing account rather than a nightly export.Chargebee
BetaThe Chargebee integration reads a Chargebee site through the v2 API with Product Catalog 2.0 semantics: item prices become plans, subscriptions carry add-ons, and invoices and transactions become charges and refunds in integer cents. Webhooks authenticated with HTTP basic auth keep subscription and dunning state current between imports.Recurly
BetaThe Recurly integration reads a Recurly site through the v3 API at version v2021-02-25, importing plans, accounts, subscriptions and transactions in that order so that references resolve as they are written. Webhook notifications are verified by HMAC signature with a five-minute replay tolerance and optional endpoint basic auth, and both US and EU data regions are supported.Paddle
BetaThe Paddle integration reads Paddle Billing — the current platform, not Paddle Classic — importing prices as plans plus customers, subscriptions, transactions and adjustments. Because Paddle is a merchant of record, its own reported fee totals are treated as authoritative, so net revenue reflects what Paddle actually remitted rather than an estimate.
2 sources
Payment processors
Payment processors know what was charged, what failed and what was refunded. They give an accurate cash picture, but a processor alone cannot tell you why a subscription changed price.
Braintree
BetaThe Braintree integration reads a merchant account through the Braintree GraphQL API and ingests real-time webhooks, importing customers, recurring billing subscriptions, transactions, refunds and disputes. Identifiers are normalised to Braintree's legacy ids throughout, because that is what the webhook payloads carry.PayPal
BetaThe PayPal integration reads billing plans, subscriptions, transactions and refunds through PayPal's REST APIs using OAuth2 client credentials, and ingests webhooks verified against a registered webhook id. It covers PayPal Subscriptions rather than one-off checkout volume, which is what makes recurring revenue metrics meaningful on a PayPal book.
2 sources
Accounting
Ledgers reconcile against recognised revenue. Connecting one is how run-rate metrics and the numbers your accountant produces stop being two unrelated stories.
QuickBooks Online
BetaThe QuickBooks Online integration reads accounting actuals through the Accounting API v3, treating recurring invoices as subscriptions and paid invoices as charges. It exists to bring booked revenue alongside billing-system revenue, so a forecast can be built on what the books say rather than on what the payment processor reports.Xero
BetaThe Xero integration reads an organisation through the Accounting API v2, mapping repeating invoices to subscriptions and paid accounts-receivable invoices to charges. Like the QuickBooks connector, it exists to put accounting actuals beside billing-system revenue rather than to replace either.
3 sources
Workflow and alerting
Where the numbers go once they exist: alerts, notifications and the tools your team already has open. These read from Bastle rather than feeding it.
Universal API
LiveBastle's write API accepts subscription data from any billing system, including one you built yourself. A single batched import endpoint upserts plans, customers, subscriptions, charges and refunds against your own external ids, and a read API returns the same metrics the dashboard renders. It is available today, self-serve, with scoped API keys.Webhooks
LiveBastle sends outbound webhooks for subscription, charge, trial and dunning events derived from every connected source, signed with an HMAC header and retried on a backoff schedule across roughly fourteen hours. Endpoints subscribe with exact event types or wildcard patterns, and delivery history is visible in settings. This is shipped and self-serve today.Slack
BetaThe Slack integration answers a slash command with live metric values from your workspace's daily snapshots and formats event alerts and scheduled metric reports as Block Kit messages. Slack never becomes a billing source — it is an output surface, and the slash command is the part that is wired end-to-end today.
2 sources
App stores
Mobile subscriptions are billed by the store, net of its commission, with renewal data that arrives on the store's own schedule. Treated as a source in their own right.
Apple App Store
BetaThe Apple App Store integration tracks auto-renewable subscription revenue for iOS apps through the App Store Server API, with real-time updates from App Store Server Notifications V2. Apple's commission is applied as the fee on each charge, so net revenue reflects the developer's actual proceeds rather than the storefront price.Google Play
BetaThe Google Play integration tracks Play Billing subscription revenue through the Android Publisher API, authenticated with a service account, and receives Real-time Developer Notifications delivered as Cloud Pub/Sub push messages. Subscription products and base plans become Bastle plans, and regional prices are converted to integer cents rather than parsed as decimals.
About these integrations
Which data sources can Bastle actually read today?
The ones on this page marked Live or Beta. Stripe is the connector Bastle is built around and the most complete path to a full metric set. Every other source carries its own status label, and a connector marked Roadmap is not built — it cannot be connected, however much the tile might wish otherwise. If a source you depend on is not listed as Live, treat it as unavailable rather than imminent.
What happens to my historical data when I connect a source?
Bastle backfills as far back as the source will serve, then keeps up with webhooks, so the first charts cover your real history rather than starting from the day you signed up. Backfill depth is a property of the upstream API, not of Bastle — some providers return the full lifetime of an account, others cap how far back their exports reach.
Does Bastle write anything back to my billing system?
Ingestion is read-only: Bastle reads plans, customers, subscriptions, charges and refunds, and does not create, modify or cancel anything upstream. Bastle never charges a card and never retries a payment on your behalf. Dunning sends email to the customer asking them to update their payment method; the payment itself is retried by your billing system under your own rules.
Can one workspace connect more than one source?
Yes. Sources are recorded per workspace and every normalised row keeps the source it came from, so a company billing through a subscription platform and taking one-off payments through a processor sees both in one metric set rather than in two dashboards. Reconciling overlapping sources — the same customer appearing in two systems — is manual work you should expect to do once.
What does an integration cost?
Nothing. Bastle is free while in beta, every connector included, with no card required and no per-source charge. There is no tier where an integration is withheld.
How do I get a connector that is not on this list?
Ask. Connector priority is set by what people actually need to connect rather than by what looks complete on a grid, so a specific request with the provider and roughly how your billing is structured is more useful than a vote. In the meantime, the API accepts normalised subscription data directly, which is how most unusual billing setups get in.
Connect one source and see your own history.
Bastle backfills what the source will serve, then keeps up over webhooks — usually a couple of minutes before the first real chart. Free while in beta, no card required.