API resources

Every Storlaunch REST resource has its own reference page in this section. Each page documents the endpoints, the request body, the response shape, the errors specific to that resource, the object schema, and the webhook events the resource emits.

This section assumes you've read:

  • Authentication — the Authorization: Bearer sk_* recipe used by every endpoint.
  • API overview — envelope, pagination, idempotency, rate limits.

If you want the full set of webhook events your endpoints can fire, jump to Webhooks → Events.

Storefront

The catalogue, fulfilment, and the unauthenticated storefront API that buyers hit when they browse and check out.

Resource Purpose
Products The catalogue: physical, digital, and licence products.
Product files Digital downloads attached to a product.
Licences License-key issuance, activation, deactivation.
Deliveries Per-order delivery records: what we sent, when.
Public storefront Unauthenticated catalogue + cart-checkout used by hosted storefronts.

Orders & operations

The post-payment surface: manual orders, stock, shipping, discount codes, payouts to the merchant.

Resource Purpose
Manual orders Phone, DM, or marketplace orders captured by hand.
Inventory Warehouses, variants, stock levels, movements.
Shipping Origin, couriers, areas, rates, shipments, labels.
Discount codes Voucher and discount-code issuance and validation.
Payouts Merchant bank account + payout lifecycle.

Payment (Plugipay-proxied)

A scoped slice of the Plugipay API exposed under your Storlaunch key. You don't mint Plugipay keys; your Storlaunch sk_* is enough.

Resource Purpose
Customers The payment-customer address book.
Checkout sessions One-shot payment flows for one-off products.
Plans Recurring-billing plans and prices.
Subscriptions Active recurring subscriptions per customer.
Invoices Hosted invoices for one-offs or subscription cycles.

Webhooks

Resource Purpose
Webhook endpoints Register, edit, and rotate webhook destinations.
API keys Mint and revoke sk_* / pk_* keys.

Conventions

Every resource shares the same response envelope, pagination protocol, idempotency keys, and error vocabulary. See:

Next