Open-source Ecommerce

June 23, 2026

Integrate and Automate Your eCommerce Backend With an Open Source Admin API

Admin APIeCommerce APIERP integrationHeadless Commerceopen source eCommerceTypeScript SDK

Spree Commerce includes an Admin API to integrate and automate your eCommerce backend. From your code you can manage the catalog, orders and customers. Connect the store to your ERP or warehouse software. Then automate the manual work between them, like order syncs and stock updates. It runs on infrastructure you own, with a fully-typed TypeScript SDK for your team.

Key Takeaways

Last verified: June 2026

What you get: an Admin API and a fully-typed TypeScript SDK for your whole eCommerce backend.

What it does: programmatically manage the catalog, orders and customers from your code.

What it connects: the other systems that run your business, from an ERP to a custom dashboard.

The win: scoped keys keep integrations safe, and bulk operations keep them fast.

What’s different with Spree Commerce: both the storefront and backend APIs are in the free core, on infrastructure you own.

Read and write your whole eCommerce backend from code

The Admin API reads and writes every resource in the store: catalog, orders, customers, promotions, gift cards, webhooks, and settings. Anything you can change in the admin, your code can change through a documented REST endpoint, added in a recent Spree Commerce release.

It is one of the most requested additions to the platform, and it is easy to see why.

Backend area	What your code can do
Catalog	Create and update products, variants, and categories
Orders	Read orders, compose draft orders, push status changes
Customers	Read and update customer records and groups
Promotions and gift cards	Manage rules, codes, and balances
Webhooks and settings	Subscribe to events and configure the store

With the Store API serving the storefront and the Admin API serving the backend, the entire platform is now headless. Every part of the store is reachable through a documented REST surface.

That shift is where the market is heading. The headless commerce market is projected to grow from $1.74 billion in 2025 to $7.16 billion by 2032 (Coherent Market Insights). A backend you can drive by API is the part that makes the rest of a headless stack practical.

What can you connect to your store?

Anything that already runs your business. The Admin API was shaped by three requests the core team kept hearing, and each one maps to a system you probably already operate.

A product team feeding the catalog from a PIM or ERP can push products, prices, and stock on a schedule instead of keying them in twice. The system of record stays the system of record, and the store reflects it.

A wholesale seller syncing orders into a warehouse system can hand each order to fulfillment the moment it is placed, then write tracking and status back to the store. No nightly export, no copy-paste.

A SaaS company embedding commerce can build a custom admin inside its own product instead of sending users to a second login. The commerce data lives behind the company’s own interface, exactly where its customers expect it.

Three different businesses, one API. That is the point of opening the backend: the store stops being an island and becomes a service your other systems talk to.

How do scoped API keys keep integrations safe?

Every key carries only the permissions you grant it. When you create a secret key, you choose which resources it can read and which it can write, so a fulfillment integration touches shipment data and nothing else. A reporting tool can be read-only across orders and customers, with no ability to change a thing.

The authentication and scopes guide covers both kinds of access: secret keys for app-to-app integrations, and token-based sessions for the custom dashboards your own team builds.

This matters more as the number of integrations grows. A store with an ERP feed, a warehouse sync, a tax service, and an internal reporting tool has four different systems reaching into the backend. Scoped keys mean a mistake or a leak in any one of them is contained to the data that key was allowed to see. You hand out exactly the access each job needs, and you can revoke any key without touching the others.

Bulk operations and draft orders for real catalogs

Real catalogs are large, so the heavy operations are built to stay fast. Bulk updates run as single database queries rather than thousands of one-at-a-time calls. Changing product status across a season’s range, assigning products to a new category, or updating customers in a group all happen in one efficient operation, so a catalog with tens of thousands of products does not grind.

Draft Orders handle the other direction. Your code can compose a complete order with line items, addresses, and promotions before it is placed, which is what a quoting tool, a sales desk, or a subscription engine needs. The order is built programmatically, then finalized like any other.

These two capabilities are what separate an API you can demo from an API you can run a business on. A backend API that falls over on a real catalog, or that cannot assemble an order from an external system, sends you back to custom work. Spree Commerce includes bulk operations and Draft Orders so the common heavy lifting is already handled.

One typed SDK for your team and your tools

The Admin API comes with a fully-typed TypeScript SDK, so your editor autocompletes every endpoint and catches a wrong field before the code ever runs. Instead of reading API docs in one window and writing fetch calls in another, your team works against types that describe the whole backend.

There is a quiet signal of quality here. The same SDK powers the React admin dashboard the core team is building on the Admin API, so every endpoint you integrate against is already exercised by a real application, not just documented. When the people who build the platform use the exact interface they hand you, the rough edges get found before you hit them.

For a team embedding commerce or building internal tools, that typed surface is the difference between a week of careful guesswork and an afternoon of building with autocomplete. And because the SDK is fully typed, an upgrade surfaces a changed field in your editor instead of at runtime, so your integration never drifts quietly out of step with the platform.

Why does open source matter for a backend API?

Because the API is only as trustworthy as your control over it. On a closed platform, the backend API is whatever the vendor exposes, hosted wherever the vendor decides, priced however the vendor chooses. With Spree Commerce, both the Store API and the Admin API are part of the free and open source core, running on infrastructure you own.

That ownership shows up in practical ways. You can read the source to see exactly what an endpoint does. You can extend the API itself when your integration needs something specific. You can deploy it in the region or the cloud your compliance team requires. And you never pay a toll to connect your own systems to your own data.

The industry has been moving this direction for years. The MACH Alliance, the industry body for modern commerce architecture, reports that a large majority of enterprises have adopted API-first, headless approaches. An open source backend API takes that one step further: it is API-first and yours to own, end to end.

This is also what makes a Spree Commerce store easy for AI coding agents to operate, a story we cover in how AI coding agents build on Spree Commerce.

Connect your eCommerce backend with the Admin API

A store is rarely the only system a business runs. The Spree Commerce Admin API lets your store join the rest of your stack as a service your code can read, write, and automate, with scoped keys for safety and a typed SDK for speed.

The payoff is the one every integration project chases, reached without the custom build. Your systems of record stay in charge, and the store reflects them in real time. Scoped keys keep each connection contained, bulk operations keep them fast on a real catalog, and the typed SDK keeps your team moving. The data never leaves infrastructure you control. And because it is open source, you can read exactly what each endpoint does and extend it when you need to.

Everything here is part of the free and open source core, so the fastest way to judge it is to connect something real.

Ready to automate your eCommerce backend? Get started with Spree Commerce, explore the headless eCommerce platform, or read the Admin API documentation.

Frequently Asked Questions