For developers

Two APIs, five SDKs, a CLI, an MCP server and agent skills — what to pick for your task.

ItemShop offers two APIs with different purposes. Every SDK has the same split.

	Storefront API v1	API with a key
What it’s for	The shop’s site, widgets, checkout	Managing the shop: products, orders, site, integrations
Where it runs	Browser (and server)	Server, CI or bot only
Authentication	None — the shop is identified by shopId or domain	X-API-Key header
Secrets	None — everything is public	A key with permissions (e.g. products:write, site:write)
In the SDK	createStorefront()	createClient({ apiKey })
Docs	Storefront API	API with a key

Pick a tool

I'm building a shop site

@itemshop/sdk + @itemshop/sdk/react and the itemshop CLI.

I'm integrating a backend / bot

The SDK in your language and an API key.

I react to events

Discord notifications about orders and daily reports.

I'm writing my own plugin

The real-time order fulfillment protocol.

I use an AI agent

The MCP server and skills for Claude Code and other agents.

I'm looking for an endpoint

The full reference generated from OpenAPI.

SDKs

Language	Package	Page
TypeScript / JavaScript	@itemshop/sdk (npm)	TypeScript
Python	itemshop (PyPI)	Python
PHP	itemshop/sdk (Composer)	PHP
Java / Kotlin	pl.itemshop:sdk (Maven)	Java and Kotlin
Go	github.com/itemshop/sdk-go	Go

TypeScript is the reference implementation. The other SDKs are generated from the same OpenAPI specification and have a hand-written, idiomatic layer — method names differ by language convention, not by meaning.

The same example in every language

The SDK pages share a layout: install → storefront → client with a key → checkout → errors. That makes it easy to compare languages:

TypeScript

const sf = createStorefront({ shopId: "65f1c0ffee0000000000abcd" });
const products = await sf.products.list();