REST API — Payments

Method	Path	What it does
GET	/api/payments/add-ons	The add-ons this workspace may buy: the org catalog’s enables_tags prices whose tags the org marks purchasable, with whether the workspace’s live subscription already holds each. An org that marks nothing purchasable sells nothing here, whatever Stripe holds.
POST	/api/payments/add-ons	Attach an add-on to the workspace’s subscription (owner only). The price must be one list_add_ons offers this workspace — a price from another org’s catalog, a plan, or a tag the org does not sell is a 404.
DELETE	/api/payments/add-ons/{price_id}	Detach an add-on from the workspace’s subscription (owner only). Not narrowed to what the org still sells: a workspace must be able to stop paying for an add-on after the org turned the tag off — the service refuses anything that is not a held add-on item.
GET	/api/payments/invoices	List invoices for the user’s workspace.
GET	/api/payments/methods	List all payment methods for the user’s workspace.
DELETE	/api/payments/methods/{payment_method_id}	Delete a payment method.
POST	/api/payments/methods/{payment_method_id}/default	Set a payment method as the default.
GET	/api/payments/plans	Return the billing plans for the request host’s org.
POST	/api/payments/setup-intent	Create (or reuse) a billing customer for the user’s workspace, then return a SetupIntent client_secret.
POST	/api/payments/subscriptions	Create a subscription for the user’s workspace.
GET	/api/payments/subscriptions/me	Return the active subscription for the current user’s workspace.