Shoporama as a headless backend
Headless commerce separates the frontend from the backend. Instead of using Shoporama’s built-in themes, you build your own frontend—a React app, a Next.js site, a mobile app, or something else entirely—and let Shoporama handle all the heavy lifting: product management, order processing, inventory management, payments, and the customer database.
This gives you total design freedom without sacrificing a proven e-commerce engine with all the features you need.
Headless API for Your Own Storefront
The REST API below is for integrations and requires an API key. For the storefront itself—which customers use in a browser or in an app—each online store has a headless API at its own URL, such as https://din-shop.dk/api. It provides the catalog, menus, Page Designer blocks, shopping cart, discount codes, checkout, payment, and customer account, and the store’s own rules for pricing, inventory, shipping, and payment apply throughout.
Shoporama’s Washington theme is built on this very API, so you can see a complete example. Get started with “Build Your Own Storefront” on Shoporama’s headless API, find all fields in the headless API documentation, and check out the Washington theme.
OAuth Login
Shoporama acts as an OAuth server, which means that third-party applications can request access to a web store via a secure login flow:
- Your application redirects the user to Shoporama’s OAuth login page with a client_id and a redirect_uri
- The user logs in with their Shoporama credentials
- The user selects which online store to grant access to and the access level (Read, Write, or Full)
- Shoporama redirects back to your app with an API token and metadata about the online store
Upon redirection, your app receives:
- An API token for REST API calls
- Shop URL and shop name
- API endpoint
- Currency and tax information
- Whether prices include or exclude tax
- Online store ID and access level
REST API with 25+ endpoints
Shoporama’s REST API provides full access to all key parts of the online store:
- Products — Create, update, delete, and retrieve products with all fields
- Categories — Manage the category hierarchy
- Orders — Retrieve orders, update status, and manage the order queue
- Customers — Create and update customer data
- Inventory — Adjust inventory levels
- Batches — Manage batch/lot numbers
- Suppliers, Brands, and Manufacturers — Product Master Data
- Product profiles and attributes — Manage variants and sizing systems
- Gift Cards — Create and manage gift cards
- Returns — Handle order returns
- Shipping — Retrieve shipping options
- Payment gateways — Retrieve configured gateways
- Pages and blog posts — Manage content
- Redirects — Manage URL redirects
- Menus — Manage the online store's menus
- Landing Pages — Create and update landing pages
- Webhooks — Manage webhooks programmatically
- Newsletters — Manage newsletter lists, subscribers, and campaigns
- Labels — Manage product labels
- Customer Fields — Manage additional customer fields
Access Levels
Tokens can be created with three access levels:
- read — Read-only access (GET requests)
- write — Write-only access (POST, PUT, DELETE)
- all — Read and write access (GET, POST, PUT, DELETE)
The access level isn’t the only restriction. An OAuth token belongs to the user who authorized the connection, and the same applies to a key created in the admin panel by a user with the Developer role. If the user has been assigned a restricted role in the online store—such as Developer, Employee, or Marketing—the token can only perform actions permitted by that role, and other requests are rejected with a 403 error. If the user is removed from the online store, the token is revoked. Read more in Roles and Permissions.
Token Security
Shoporama takes token security seriously:
- Rate limiting — Automatic limitation of the number of requests to protect against abuse
- Usage statistics — Detailed log of all API calls per token, including method, endpoint, IP address, and user agent
- Automatic revocation — If the user who authorized an OAuth connection is logged out of the online store, the token is automatically revoked
- Revocation — Tokens can be manually revoked at any time
- Last-used tracking — See when each token was last used
Typical use cases
- Custom frontend: Build a React/Next.js frontend that fetches product data from Shoporama
- Mobile app: Create a native iOS/Android app with Shoporama as the backend
- ERP integration: Synchronize products and orders with your ERP system
- POS system: Connect your in-store system to your online store
- Marketplace integration: Push products to Amazon, eBay, or other marketplaces
- Custom apps: Build apps that extend Shoporama’s functionality