Conventions
Every snippet uses the TypeScript SDK. Request and response bodies mirror what the live API returns — real field names, real structure. Ids, names, and emails are illustrative (John Doe,
example.com); the shapes around them are exact.
Two clients appear throughout. Read endpoints (catalog, search, pricing) take a publishable key and
are safe in the browser; writes that touch money or another customer’s data (orders, payments) take
a secret key and run on your server. Each step names the client it uses.
The Key Usage by Endpoint table maps every endpoint to
pk / sk / customer-session / HMAC. Each step on the pages below also names the credential it
takes.The use cases
Storefront checkout
The core journey: browse the catalog, build a cart, sign the shopper in, quote shipping, place
the order, and take payment — guest-to-paid in one sequence.
Search & discovery
Text + semantic search, AI recommendations, browsing behavior capture, and dynamic pricing —
the discovery surfaces that get shoppers to the cart.
Returning customer
Sign-in, order history, lodging and tracking a return, and applying store credit on the next
order.
Reviews & messaging
Post-purchase engagement: submit and vote on reviews, and run a real-time customer ↔ store
conversation.
Marketplace
Operator flows for a multi-merchant marketplace: aggregated discovery, a unified split
checkout, and a shopper’s cross-merchant profile.
Catalog sync
Push your external catalog into Galactic Core (and publish it back out) — feed formats,
validation, and the secure ingestion handshake.
Webhooks & automation
React to commerce events in real time — register an endpoint, verify deliveries, and handle
order.paid end to end.