Overview

The Admin API is Loop's server-to-server API surface. It's built for the store's back end, not the customer. Anything the store's server, ERP, OMS, or internal system needs to do across the whole store runs through this surface.

Rule of thumb: if the server performs the action, use Admin. If the logged-in customer performs it themselves in a UI, use the Storefront API instead.

Authentication

Single API token, sent as X-Loop-Token on every request
Generated from Loop admin portal under Settings > API Tokens

POST https://api.loopsubscriptions.com/admin/2026-04/{endpoint}
X-Loop-Token: <your_admin_api_token>
Content-Type: application/json

Base URL

https://api.loopsubscriptions.com/admin/2026-04/

Rate limits

Enforced per store, shared across all API keys on that store.

Global pool: 50 requests/second/store for most endpoints
Endpoint specific overrides: View the full list here
Heavy list endpoints (all subscriptions, all orders, all customers, etc.) draw from small, isolated pools instead of the global 50 rps

For large syncs, use webhooks plus incremental pulls rather than brute-force pagination against list endpoints. Learn more about Loop's api rate limit here

Typical use cases

Programmatic subscription creation and management
Bulk operations across subscribers
ERP, OMS, and 3PL synchronization
Analytics pulls and data warehouse sync

Key constraints

Loop is Shopify-native. Subscriptions can't exist independently of Shopify; the Admin API manages them, it doesn't create them outside Shopify
Some admin-side configuration (cancellation offers, upsell profiles, gift programs, loyalty features) is set up in the Loop admin dashboard, not defined via API
A few capabilities require entitlement from the account's success manager. Confirm access before committing scope or a date