Skip to main content
Every Admin API resource is exposed as a property on the client (client.orders, client.products, …). Collection resources follow a consistent CRUD shape — list, get, create, update, delete — plus resource-specific actions. Nested resources take the parent ID as the first argument: For the underlying HTTP surface — every endpoint with the API key scope it requires — see the Admin API endpoint index.

Catalog

Orders & fulfillment

Customers

Pricing & promotions

Inventory

Sales channels

Store configuration

Platform & access

Custom fields

Resources that support custom fields (products, variants, orders, customers, categories, option types) expose a customFields accessor taking the parent ID first:
The generic escape hatch covers any owner type:

Adding your own resources

The resource map grows with your store. The spree generate api_resource generator scaffolds new Admin API endpoints (model, serializers, controllers, routes, specs) in one command — then call them from the SDK with a custom fetch or raw request, or generate a typed client for them.