> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.fluveo.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fluveo.com/_mcp/server. # 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](/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 **17 resources** are in the contract and appear in the [API Reference](/api-reference): | Resource | Notes | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Payment Intents | Create → confirm → capture → cancel lifecycle | | Charges | Read-only projection | | Customers | Create, retrieve, update, delete (not available for US Stripe Connect stores), list | | Payment Methods | Read-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` | | Refunds | Create, retrieve, update, list (first page; `starting_after`/`ending_before` accepted but not yet paged — use `limit`) | | Balance | Retrieve | | Balance Transactions | Retrieve, list | | Checkout Sessions | Create, 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 Endpoints | Management: create, retrieve, update, list, delete. Per-endpoint `whsec_` secret and per-event routing via `enabled_events`. **Signed delivery is live** — see [Webhooks](/webhooks) | | Events | List (first page; filter by `limit` + `type`) and retrieve | | Payment Links | API live (platform-key); merchant `sk_` blocked, dashboard-managed. Create, retrieve, update, list — backed by real Payment Intents — plus the public hosted page `GET /p/{plink_id}`. Create takes Stripe's `line_items` (`price` or `price_data`). See [Payment Links](/checkout/payment-links) | | Setup Intents | Six TEST operations (create, retrieve, update, confirm, cancel, list). List is a tenant-scoped Stripe list envelope from `merchant_setup_intents`; it never returns processor-wide rows. See [Setup Intents](/resources/setup-intents) | | Subscriptions | Billing endpoint. Create, retrieve, list, and period-end cancel | | Invoices | Billing endpoint. Create, retrieve, list, and finalize | | Invoice Items | Billing endpoint. Create | | Products | Billing endpoint. Create, retrieve, list, update, delete. Delete is refused while any price references the product, so archiving (`active=false`) is the usual verb. Search is not served | | Prices | Billing endpoint. Create, retrieve, list, update. Update changes only `active`, `nickname`, `lookup_key`, `tax_behavior` and `transfer_lookup_key` — amount, currency and product are immutable, as they are in Stripe. Tiered, package, customer-chosen, per-currency and metered pricing are unsupported. Search is not served | ## 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](/api-reference). They're documented in the [Checkout](/checkout/overview) and [Billing](/billing/overview) sections. | Resource | Note | | --------------- | -------------------------------------------------------------------------------------------------------------------- | | Coupons | Billing endpoint, served but not yet in the contract | | Promotion Codes | Billing endpoint, served but not yet in the contract | | Credit Notes | Billing endpoint, served but not yet in the contract. Direct creation is refused while money movement is unavailable | | Tokens | Card tokenization route is mounted; tokenization is **PCI / card-vault gated** (see [Tokens](/resources/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 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. | Resource | Note | | --------------------------------------------------- | ---------------------------------------------------------------- | | Disputes | `404 unsupported` on `/v1` — see [Disputes](/resources/disputes) | | Payouts | `404 unsupported` on `/v1` — see [Payouts](/resources/payouts) | | Mandates | `404 unsupported` on `/v1` — see [Mandates](/resources/mandates) | | Files | `404 unsupported` on `/v1` | | Tax, Issuing, Treasury, Terminal, Identity, Connect | `404 unsupported` on `/v1` | In total: **12 live (in the API Reference)** · **9 served but not yet contracted** · **0 not on `/v1` yet** · **10 unsupported on `/v1`**. ## SDKs SDKs are not supported, including the official Stripe SDKs. Call the API directly (see the curl examples in the [API Reference](/api-reference)). The supported path is the `/v1` HTTP API, the Fluveo integration skill for AI coding agents, and the published API Reference. See [Migrate from Stripe](/guides/migrate-from-stripe).