Get started with Thor

This path is for developers connecting a trusted management service, building a buyer-facing storefront, or doing both. It establishes the project boundary and gets each API to a working response before introducing deeper commerce rules.

Before you begin

You need a Thor project slug and the credentials supplied for your environment. Admin requests require an Admin user token or API key. Protected Storefront projects require a storefront token; customer access tokens are created later by customer account flows.

For the Storefront path, prepare or create an active store with distribution, price, and supply context plus at least one active, published variant with an eligible price.

Follow the sequence

  1. How Thor fits together — see how project configuration becomes runtime catalog, cart, and order data.
  2. Connect to a project — choose the endpoint, credential, and browser/server boundary.
  3. Make your first Admin API request — run a read and a safe draft-product mutation.
  4. Make your first Storefront API request — query one prepared catalog context and create a cart.
  5. From product to first order — connect the configuration and runtime steps with one test fixture.

Choose your next entrance

Use Commerce concepts when you need to understand resource behavior or lifecycle. Use Developer guides when you have a concrete implementation outcome. Use the Admin API or Storefront API reference when you need an exact field or operation contract.