Reference

API coverage

The Fluveo /v1 API is Stripe-shape-compatible. This page is the honest map of what actually responds today, derived from the live API and its canonical OpenAPI contract.

There are three things worth separating, because they are not the same:

  • In the contract — the resource is in the canonical contract, so it appears in the interactive API Reference with schemas and try-it.
  • Served on /v1 — the route is mounted and responds (it may be served even if it is not yet in the contract, so it won’t show in the generated reference).
  • Not supported on /v1 — the route returns a documented Stripe-shaped 404 on purpose; it is a bounded non-launch surface, not an imminent feature.

Live now (launch contract)

These 11 resources are in the contract and appear in the API Reference:

ResourceNotes
Payment IntentsCreate → confirm → capture → cancel lifecycle
ChargesRead-only projection
CustomersCreate, retrieve, update, delete, list
Payment MethodsRead-only: retrieve + a customer-scoped list (nested /customers/{id}/payment_methods and top-level ?customer=). Account-wide list (no customer) and attach/detach/create return 404 unsupported_operation
RefundsCreate, retrieve, update, list (first page; starting_after/ending_before accepted but not yet paged — use limit)
BalanceRetrieve
Balance TransactionsRetrieve, list
Checkout SessionsCreate, retrieve, update, list, line_items, expire — backed by real Payment Intents — plus the public hosted payment page GET /c/{cs_id}. Session lifecycle events (checkout.session.*) are not yet emitted
Webhook EndpointsManagement: create, retrieve, list, delete, rotate_secret. Per-endpoint whsec_ secret and per-event routing via enabled_events. Signed delivery is live — see Webhooks
EventsList (first page; filter by limit + type) and retrieve
Payment LinksAPI live (platform-key); merchant sk_ blocked, dashboard-managed. Create, retrieve, update, expire, list — backed by real Payment Intents — plus the public hosted page GET /p/{plink_id}. Flat amount/currency create (a deliberate divergence from Stripe’s line_items/price); expires_at is a Fluveo extension. See Payment Links

Live in code — not in the API Reference yet

These routes are served on /v1 today, but are not yet in the contract, so they don’t appear in the generated API Reference. They’re documented in the Checkout and Billing sections.

ResourceNote
SubscriptionsBilling endpoint — requires the Stripe-Version: 2024-09-30.acacia header
InvoicesBilling endpoint — same version header
Invoice ItemsBilling endpoint — same version header
ProductsBilling endpoint — same version header
PricesBilling endpoint — same version header
CouponsBilling endpoint — same version header
Promotion CodesBilling endpoint — same version header
Credit NotesBilling endpoint — same version header
TokensCard tokenization route is mounted; tokenization is PCI / card-vault gated (see Tokens)

Why aren’t these in the API Reference? The reference is generated from a machine-checked OpenAPI contract. Adding a served route to that contract is a deliberate, separately-reviewed step — until it lands, the route works but isn’t in the generated reference.

Not on /v1 yet

The product capability exists, but there is no Stripe-shaped /v1 API for it yet.

ResourceNote
Setup IntentsNo /v1/setup_intents route yet (404). See Setup Intents

Not supported on /v1 (documented 404)

These return a documented Stripe-shaped 404 unsupported by design — a bounded, non-launch surface, never a fake partial-parity success. Some belong to resources whose webhook event types are still accepted on an endpoint but stay dormant until the resource ships.

ResourceNote
Disputes404 unsupported on /v1 — see Disputes
Payouts404 unsupported on /v1 — see Payouts
Mandates404 unsupported on /v1 — see Mandates
Files404 unsupported on /v1
Tax, Issuing, Treasury, Terminal, Identity, Connect404 unsupported on /v1

In total: 11 live (in the API Reference) · 9 served but not yet contracted · 1 not on /v1 yet · 10 unsupported on /v1.

SDKs

Fluveo does not publish SDKs yet. Call the API directly (see the curl examples in the API Reference), or point an existing Stripe client such as stripe-node or stripe-python at https://api.fluveo.dev for the operations listed above. See Migrate from Stripe.