Networks
A network is the multi-party shared ledger space partners write into. The public HTTP contract addresses a network by networkId — it does not expose a list/get-networks API.
Maturity: Docs v0 · Early Access. See Integration Surfaces.
Unit of record
The unit of record is shared sealed / multi-party state on a network. Wallet routes and webhook ingest write into that state. Day-2 shared-space membership and ledger-application lifecycle are operator concerns (Network Ops), not the partner wallet contract.
Partners
| To answer | Do this |
|---|---|
| Which network does my key belong to? | GET /token-gateway/whoami with X-Api-Key — returns networkId and gateway URLs |
| Call wallet ops on that network | Paths under /token-gateway/{networkId}/… — see Tokens |
| Write arbitrary JSON via webhook | POST to the ingest URL for that network — see Webhook ingest |
| List every network I own via public HTTP | Not available — use the signed-in dashboard |
curl -sS \
-H "X-Api-Key: $STRATUM_API_KEY" \
"https://token-gateway.blockskunk.com/token-gateway/whoami"
Copy the exact token-gateway / ingest hosts from Dashboard → API Keys when they differ from the examples in these docs.
Operators
Signed-in operators provision and manage networks in the dashboard:
| Capability | Where |
|---|---|
| List / open my networks | Dashboard deployments list |
| Mint / rotate API keys scoped to a network | Developer → API Keys |
| Webhook URL for that network | Same API Keys card (ingest host + networkId) |
| Day-2 shared space create / join / status | Network Ops panel on the deployment |
| Ledger-application install / commit / policy | Network Ops + Developer tools package upload |
| Ingest auth detail (key format, revoke) | Gated Developer API → Authentication |
Network Ops
Day-2 Network Ops runs as signed-in dashboard actions (same flows the Network Ops panel uses). They reach the node through the management plane — not your partner X-Api-Key, and not public OpenAPI.
| Action | Who | Effect |
|---|---|---|
| Create shared space | Host operator | Opens a shared space, publishes join material for partners, joins the local node |
| Join shared space | Host or partner | Joins after join material exists; verifies local node membership before success |
| Shared space status | Any operator | Membership + height; heals sticky UI only when the live node list succeeds |
| Status callback | Node startup scripts | Writes created/joined status back to the control plane |
| Install ledger application | Operator | Install package on the node (upload from Developer tools first) |
| Commit ledger application | Operator | Approve + commit + query committed |
| Update signature policy | Operator | Approve + commit with a new signature policy |
Shared space names must match /^[a-z][a-z0-9-]{0,249}$/.
Join is not multi-party approval. Join is a local node operation after join material exists. Shared spaces today are single-org (host); listing intended member orgs on create is product intent for discovery, not a multi-org config update yet.
The deployment Activity tab records create/join success and failure. Prefer the Network Ops panel for day-to-day work. Full operator samples stay under signed-in Network admin.
What is not public
Per the Disclosure Boundary:
- No public HTTP list/get of networks or deployments
- No public day-2 shared-space or lifecycle HTTP routes (node admin paths and operator samples stay signed-in)
- No node hostnames, operator service-account auth, or join-material storage paths
Partner integrations stay on token gateway + webhook ingest with dashboard-minted keys.