SDKs
Storlaunch ships SDKs in three languages, with feature parity across all three. Pick the one for your stack:
| Language | Package | Install |
|---|---|---|
| Node.js | @forjio/storlaunch-node |
npm install @forjio/storlaunch-node |
| Python | storlaunch |
pip install storlaunch |
| Go | github.com/hachimi-cat/saas-storlaunch/sdk/go |
go get github.com/hachimi-cat/saas-storlaunch/sdk/go |
All three:
- Implement the same surface: every API resource is exposed as a typed method.
- Handle bearer-token authentication automatically — you hand in the API key, they set the header on every request.
- Provide a
verifyWebhookhelper for inbound events. - Use only minimal dependencies (Node: zero runtime deps; Python:
httpx; Go: stdlib). - Are open source: code is in the saas-storlaunch repo under
sdk/<lang>/.
When to use which
If your existing stack is in Node, Python, or Go: use the matching SDK. There's no perf or feature reason to use one over another — pick your language.
If your stack is in another language (Ruby, PHP, Rust, Java, Elixir, etc.): use the raw API. Authentication is just a bearer header — we have customers integrating in all of those languages without an SDK. We don't currently plan to publish SDKs in additional languages, but if there's strong demand, email us.
What's covered
The SDK surface mirrors the API surface 1-for-1:
- Storefront —
products,licenses,deliveries,public - Inventory —
inventory - Orders —
manualOrders,discountCodes - Shipping —
shipping(zones, rates, labels) - Customers — buyer accounts, addresses
- Account —
apiKeys,auditLog,domains,account,onboarding,modules - Payments (Plugipay proxy) —
checkoutSessions,plans,subscriptions,invoices,receipts,customers,portalSessions,webhookEndpoints,webhookEvents - Marketing (Ripllo proxy) —
pixels,abandonedCart,feeds,blog,referrals - Analytics & reports —
analytics,reports,payouts,ledger
See each SDK's README for the full method list.
Quick comparison
Same call in three languages — list the first 10 products in a workspace:
Node.js:
import { StorlaunchClient } from '@forjio/storlaunch-node';
const storlaunch = new StorlaunchClient({
apiKey: process.env.STORLAUNCH_API_KEY!,
});
const products = await storlaunch.products.list({ limit: 10 });
Python:
from storlaunch import StorlaunchClient
import os
storlaunch = StorlaunchClient(api_key=os.environ["STORLAUNCH_API_KEY"])
products = storlaunch.products.list(limit=10)
Go:
import storlaunch "github.com/hachimi-cat/saas-storlaunch/sdk/go"
client, _ := storlaunch.NewClient(storlaunch.ClientOptions{
APIKey: os.Getenv("STORLAUNCH_API_KEY"),
})
products, _ := client.Products.List(ctx, storlaunch.ListParams{Limit: 10})
The differences are purely idiomatic: camelCase in Node, snake_case in Python, PascalCase in Go. The underlying API call is identical.
Versioning
All SDKs follow semantic versioning:
- MAJOR bumps for breaking changes (rare; we'll batch them).
- MINOR bumps for new features.
- PATCH bumps for fixes.
Current versions:
- Node:
0.x(active) - Python:
0.x(active) - Go:
0.x(active)
Pre-1.0 means we may still make small breaking changes between minor versions. We document every break in the changelog. Once we hit 1.0 (target: mid-2026), the major/minor/patch contract becomes strict.
Open-source
The SDKs live in the same repo as Storlaunch itself:
- Node: saas-storlaunch/sdk/node
- Python: saas-storlaunch/sdk/python
- Go: saas-storlaunch/sdk/go
Contributions welcome. PRs go through the same review as the rest of the codebase. Issues at github.com/hachimi-cat/saas-storlaunch/issues.
Webhooks
Each SDK ships a verifyWebhook helper. Pass the raw request body, the X-Storlaunch-Signature header, and the endpoint's signing secret; get back a typed event you can switch on.
Node:
import { StorlaunchClient, type WebhookEvent } from '@forjio/storlaunch-node';
const event: WebhookEvent = storlaunch.webhooks.verify({
body: rawBody,
signature: req.headers['x-storlaunch-signature']!,
secret: process.env.STORLAUNCH_WEBHOOK_SECRET!,
});
switch (event.type) {
case 'order.paid': /* ... */ break;
case 'order.fulfilled': /* ... */ break;
}
The Python and Go SDKs expose the same primitive idiomatically.
Coming pages
Per-language deep references (installation notes, advanced usage, every method) will land at:
/docs/sdk/node/docs/sdk/python/docs/sdk/go
For now, the SDK READMEs on GitHub are the source of truth.
Next
- Installation — if you haven't installed an SDK yet.
- Concepts — the data model the SDKs expose.
- API reference — the underlying HTTP API.