ForjioHuudisIdentityPlugipayPaymentsStorlaunchE-commerceFulkrumaFulfilmentRiplloMarketingLinkSnapShort URLsPawpadoGPU streaming
Storlaunch Docs
⌘K

Installation

Storlaunch ships SDKs in three languages so you can drive the platform — products, orders, fulfilment, customers — from your own code. Pick the one that fits your stack:

  • SDK — libraries in Node.js, Python, and Go. Best for embedding Storlaunch in an application or syncing inventory from another system.
  • Raw API — if you can't or don't want to add a dependency, the REST API is fully documented and authenticated with a plain Authorization: Bearer header.

This page covers installing the SDKs. If you want raw API access, skip ahead to API authentication.

Node.js SDK

The Node SDK is @forjio/storlaunch-node:

npm install @forjio/storlaunch-node

Or with pnpm / yarn:

pnpm add @forjio/storlaunch-node
yarn add @forjio/storlaunch-node

It's compatible with Node 20 and later. It ships with TypeScript types out of the box — no @types/* package needed.

Minimal usage:

import { StorlaunchClient } from '@forjio/storlaunch-node';

const storlaunch = new StorlaunchClient({
  apiKey: process.env.STORLAUNCH_API_KEY!,
});

const products = await storlaunch.products.list({ limit: 10 });
console.log(products);

The full reference is at SDK → overview.

Python SDK

The Python SDK is published on PyPI as storlaunch:

pip install storlaunch

It supports Python 3.9+. Dependencies: httpx only.

Minimal usage:

from storlaunch import StorlaunchClient
import os

storlaunch = StorlaunchClient(api_key=os.environ["STORLAUNCH_API_KEY"])

products = storlaunch.products.list(limit=10)
print(products)

Go SDK

The Go SDK lives in the same repo as Storlaunch itself:

go get github.com/hachimi-cat/saas-storlaunch/sdk/go

Import it as storlaunch:

import storlaunch "github.com/hachimi-cat/saas-storlaunch/sdk/go"

It uses only the Go standard library — no external dependencies. Requires Go 1.22+.

Minimal usage:

package main

import (
    "context"
    "fmt"
    "os"

    storlaunch "github.com/hachimi-cat/saas-storlaunch/sdk/go"
)

func main() {
    client, err := storlaunch.NewClient(storlaunch.ClientOptions{
        APIKey: os.Getenv("STORLAUNCH_API_KEY"),
    })
    if err != nil {
        panic(err)
    }

    products, err := client.Products.List(context.Background(), storlaunch.ListParams{Limit: 10})
    if err != nil {
        panic(err)
    }
    fmt.Println(products)
}

Get your API key

All three SDKs need a Storlaunch API key. To get one:

  1. Sign up at storlaunch.forjio.com — takes about a minute. See Quickstart for the details.
  2. Open the dashboard and go to Settings → API keys.
  3. Click Create API key. Pick Test for development.
  4. Copy the key value immediately — we don't show the secret again.

The convention across SDKs is to read the key from an environment variable:

Variable Purpose
STORLAUNCH_API_KEY Secret API key — never commit, never log
STORLAUNCH_BASE_URL Optional — only set if you're pointing at staging or a self-hosted Storlaunch instance

Don't bake the key into source. Use your environment's secret manager. For local dev, a gitignored .env file plus dotenv is fine. For production, use AWS Secrets Manager, Vault, or your platform's equivalent.

Test vs live keys

Storlaunch keys are prefixed with their environment:

  • sk_test_… — test environment. Orders are simulated end-to-end, no real money, no real shipments.
  • sk_live_… — live environment. Real orders, real money, real fulfilment.

The base URL is the same; Storlaunch routes the request to the correct environment based on the key. You can run test and live in parallel — create both keys, store them under different env-var names, switch by setting which one is exported.

Publishable vs secret keys

Storlaunch issues two kinds of keys:

  • Publishable (pk_*) — safe to embed in a public storefront's JavaScript. Read-only access to public product data.
  • Secret (sk_*) — full account access. Server-side only.

The SDKs accept either, but most server-side code uses a secret key. Publishable keys are for the storefront frontend — the auto-generated Storlaunch storefront uses them by default.

Sandbox & staging

If you want to test against a non-production Storlaunch instance, point any SDK at staging:

export STORLAUNCH_BASE_URL=https://api-staging.storlaunch.forjio.com

Test keys minted in production don't work in staging and vice versa. We can issue staging keys on request — email hello@storlaunch.forjio.com if you're building an integration that needs them.

Next: take a test order

You're ready. Head back to the Quickstart for the end-to-end walkthrough, or jump to Concepts for the data model.