Stripe

Stripe (via Apideck)

Access Stripe through Apideck's Accounting unified API — one of 34 Accounting connectors that share the same method surface. Code you write here ports to Access Financials, Acumatica, banqUP and 30 other Accounting connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Stripe plumbing.

Quick facts

• Apideck serviceId: stripe
• Unified API: Accounting
• Auth type: oauth2
• Apideck setup guide: Connection guide
• Gotchas: page
• Stripe docs: https://stripe.com/docs/api
• Homepage: https://stripe.com/

When to use this skill

Activate this skill when the user explicitly wants to work with Stripe — for example, "create an invoice in Stripe" or "reconcile payments in Stripe". This skill teaches the agent:

1. Which Apideck unified API covers Stripe (Accounting)
2. The correct serviceId to pass on every call (stripe)
3. Stripe-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• Accounting: https://specs.apideck.com/accounting.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List invoices in Stripe
const { data } = await apideck.accounting.invoices.list({
  serviceId: "stripe",
});

Portable across 34 Accounting connectors

The Apideck Accounting unified API exposes the same methods for every connector in its catalog. Switching from Stripe to another Accounting connector is a one-string change — no rewrite, no new SDK.

// Today — Stripe
await apideck.accounting.invoices.list({ serviceId: "stripe" });

// Tomorrow — same code, different connector
await apideck.accounting.invoices.list({ serviceId: "access-financials" });
await apideck.accounting.invoices.list({ serviceId: "acumatica" });

This is the compounding advantage of using Apideck over integrating Stripe directly: code against the unified Accounting API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Stripe via Apideck Accounting

Stripe is the dominant online payments platform. Apideck surfaces Stripe's accounting-adjacent resources (customers, invoices, payments, refunds) through the unified Accounting API — not the full Stripe surface.

Scope: use this connector when you want to read Stripe data as part of an accounting workflow (invoices, payments, tax). For subscription management, Stripe Elements, Connect, or Terminal, go direct to Stripe's API or use the Proxy.

Entity mapping

Stripe entity	Apideck Accounting resource
Invoice	invoices
Customer	customers
PaymentIntent / Charge	payments
Refund	refunds
Credit Note	credit-notes
Tax Rate	tax-rates
Invoice Item	invoice-items
Account	company-info
Bank Account	bank-accounts
Expense	expenses

Coverage highlights

• ✅ Invoices and invoice items
• ✅ Customers
• ✅ Payments / charges
• ✅ Refunds (critical for reconciliation workflows)
• ✅ Tax rates
• ⚠️ Bills / supplier AP concepts — not meaningful in Stripe (no AP); treat as empty
• ❌ Subscriptions, plans, pricing — use Proxy or the Stripe SDK directly
• ❌ Connect (multi-party) flows — complex; use Proxy
• ❌ Webhooks — use Stripe's webhook endpoints directly, not the Apideck unified webhook

Auth notes

• Type: OAuth 2.0 (Stripe Connect flow) — managed by Apideck Vault
• Account binding: one Stripe account per connection. Connect-based marketplaces need per-seller connections.
• Test vs live mode: Stripe distinguishes test and live keys. Ensure the user authorizes the intended mode during Vault OAuth.
• Alternative for accounting reconciliation: many teams already use Stripe's own data sync to QuickBooks/Xero. Apideck via Stripe is best when you need unified data across multiple providers (e.g., Stripe + QuickBooks).

Example: list customers with payment totals

const { data } = await apideck.accounting.customers.list({
  serviceId: "stripe",
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Accounting unified API, use Apideck's Proxy to call Stripe directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Stripe's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: stripe" \
  -H "x-apideck-downstream-url: <target endpoint on Stripe>" \
  -H "x-apideck-downstream-method: GET"

See Stripe's API docs for available endpoints.

Sibling connectors

Other Accounting connectors that share this unified API surface (same method signatures, just change serviceId):

access-financials (beta), acumatica (beta), banqup (beta), campfire (beta), clearbooks-uk (beta), digits (beta), dualentry, exact-online, and 25 more.

See also

• Apideck connection guide for Stripe
• Accounting OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Stripe official docs