Admin API
Full read and write access to one marketplace, with the rights of its administrator: users, listings, categories, orders, events, collections, shipping and payment settings. For servers only.
What you can build
A Kreezalid marketplace works without code: its owner sets it up in the back office, vendors
publish listings, customers order. Everything that goes beyond that is done from the outside,
with five building blocks. Each one is scoped to one marketplace and is served from that
marketplace’s own address, for instance https://acme.mykreezalid.com.
The building blocks
Section titled “The building blocks”Front API
The API of a signed-in member: sign-up and login, account, cart, checkout addresses, the member’s orders, wishlist, a vendor’s own listings. Callable from a browser or a mobile app.
Partners API
The API of one vendor: their listings, their orders, their stores and shipping rates. For the ERP, PIM or warehouse system of a vendor.
Webhooks
A signed HTTP request to your URL when a user, a listing or an order changes. The way to react in real time instead of polling.
Themes
The storefront and its emails are Liquid templates you can edit, with HTML, CSS and JavaScript, from the back office.
MCP server
Lets an AI agent read how the marketplace is built and reconfigure it (categories, attributes, order types, pages…) after an administrator approves the connection.
Which one should you use?
Section titled “Which one should you use?”| You are building… | Use | Why |
|---|---|---|
| A sync between the marketplace and an ERP, a CRM or a data warehouse | Admin API + webhooks | Sees every user, listing and order of the marketplace. Webhooks push changes, the API reads and writes back. |
| A catalog import from a spreadsheet or a supplier feed, run by the marketplace owner | Admin API | Creates listings for any vendor, in bulk. See Import a catalog. |
| The connector of one vendor’s own back-office system | Partners API | The credential only reaches that vendor’s listings, orders and stores. |
| A mobile app or a JavaScript front end for members | Front API | Members sign in with their own email and password and receive a token. No secret ships in the app. |
| A custom look, new storefront sections, edited emails | Themes | Server-rendered Liquid, edited in the back office. |
| Setting up or restructuring a marketplace with Claude, ChatGPT or Cursor | MCP server | The agent previews every change before applying it, so it can show you the plan first. |
What each API can reach
Section titled “What each API can reach”| Capability | Admin API | Partners API | Front API |
|---|---|---|---|
| Read and write listings, variants, add-ons, listing metafields | All vendors | The vendor’s own | The signed-in vendor’s own |
| Categories and listing attributes | Read and create categories, read attributes | Read | Read |
| Users and user metafields | Read, create, update, delete | — | The signed-in member’s own account |
| Orders and order metafields | All orders: read, update status and fields | The vendor’s orders: read, update | The member’s orders, as customer or vendor |
| Cart and checkout addresses | — | — | Yes |
| Record a payment made outside Kreezalid | POST /api/v1/checkout/preauth-success |
— | — |
| Stores (physical shops, pickup points) | — | Yes | — |
| Events log | Yes | — | — |
| Collections and collection models | Yes | — | — |
| Wishlists (listings and vendors) | — | — | Yes |
Start here
Section titled “Start here”QuickstartGet credentials, make your first call and create a listing, in five minutes.
Core conceptsUsers and groups, listings, carts, orders and their statuses, as the APIs name them.
Get a test marketplaceStart a free trial and fill it with sample data to build against.
AuthenticationHow each API authenticates, and what it answers when credentials are wrong.