The Apps API is in beta. Its endpoints and responses may change.
- Connecting and configuring Stripe or Wix Payments
- Managing a Stripe product and price catalog
- Reading payment analytics
- Recognizing the webhook traffic the providers send back to Base44
Prerequisites
- A personal access token. See Authentication to get one.
- An app you can edit. Most operations here require write access, not just read access.
App ID
Endpoints that act on a specific app include the app’s ID in the URL path asapp_id.
To get your app ID:
- Go to app.base44.com.
- Open your app in the app editor.
- Copy the app ID from the editor URL:
"https://app.base44.com/apps/<app_id>/editor".
Two independent providers
An app connects to Stripe, Wix Payments, or the legacy Payments by Wix integration. These are separate setups with separate credentials, so connecting one does not affect the others’ stored state, except for Install Stripe integration. The analytics and dashboard-link endpoints take a provider-specific path rather than a shared one.Inbound payment webhooks
Base44 registers the webhook endpoints under Webhooks with the payment provider for you, and the provider is the only caller. You can’t invoke them for your own app or repoint them. They’re documented so you can recognize the traffic and read the acknowledgements they return.
status coming back as processed, acknowledged, ignored, or (Stripe only) logged, plus an optional reason or action explaining it. These endpoints authenticate the provider’s signature instead of a Base44 personal access token, so they carry no Authorization header requirement.
A verified event that fails processing returns an error so the provider retries it. An event Base44 can’t attribute to an app, such as one missing the app ID it expects back, is acknowledged as ignored rather than failed.
Payment analytics
These three endpoints read the same payment activity from different angles:- Get payment analytics: totals and a daily trend
- Get recent payment transactions: the latest individual payments, refunds, and disputes
- Get top payment customers: who’s paid the most
Transactions
These four endpoints work with individual transactions rather than aggregated summaries, and need write access to the app:- List payment transactions: every payment, refund, and lost dispute, paged, across the app’s whole history
- Export payment transactions: the same history as a CSV file
- Get payment transaction: one payment in full, read live from its provider
- Refund payment transaction: refund all or part of a payment
Rate limits
Provision live Stripe keys has its own base limit, scoped to your account rather than the workspace, documented on its own rate-limit response. See Rate limits for the base limit that applies to every other operation here, and for the multiplier your plan gets on both.Endpoints
Setup and catalog endpoints are on the page for each provider:- Stripe: Set up Stripe, move from sandbox to live, and manage products and prices.
- Wix Payments: Connect Wix Payments, switch test mode, and open its dashboard.
Analytics
- Get recent payment transactions: Read the app’s most recent payments, refunds, and disputes.
- Get top payment customers: Rank customers by live payment amount or count.
Transactions
- List payment transactions: Read one page of payments, refunds, and lost disputes for one provider.
- Export payment transactions: Download transactions for one provider as a CSV file.
- Get payment transaction: Read one payment in full from its provider.
- Refund payment transaction: Refund all or part of a payment.
Webhooks
- Receive Stripe sandbox event: The endpoint Base44 registers with Stripe for sandbox events.
- Receive Stripe live event: The endpoint Base44 registers with Stripe for live events.
- Receive Wix Payments event: The endpoint Base44 registers with Wix Payments.