Does Zubs have an API for subscriptions?
What can I build with the Zubs API?
Anything that needs your subscription data outside Shopify and the Zubs admin. For example:
- Your own app. Subscribers see their subscriptions, their next delivery and what’s in it, right in your app.
- Your back office. Pull upcoming deliveries into your planning, or show a customer’s subscriptions in the tools your support team uses.
- Automated changes. Swap a discontinued product across subscriptions, or adjust upcoming orders from your own system.
- Reporting. Load subscriptions, billing history and the subscription timeline into your own dashboards.
What does the customer API do?
The customer API is for apps your subscribers use. They sign in with their Shopify customer account, with the same email and one-time code as in your store, so there’s no new password. Zubs handles the sign-in with Shopify, and your app gets access to that subscriber’s subscriptions.
Your app shows the subscriptions natively and can take the common actions directly: skip or reschedule a delivery, ship one now, pause, resume or cancel. For changes to products, quantities or the delivery interval, we recommend opening the Zubs customer portal from your app. It already handles your stock and pricing, and subscribers are already signed in there.
A subscriber only reaches their own subscriptions. Requests for anyone else’s data, or for store settings, are turned away.
What does the Admin API do?
The Admin API is for your own servers. It reads and changes the subscriptions in your store without a subscriber signing in, so your back office, helpdesk or reports can use the same data your customers see. Besides the actions of the customer API, your systems can change what’s in a subscription: products, quantities, delivery interval, discounts and single upcoming orders. That suits server-to-server integrations and automated processes.
Access is per store. Your developers get a private key that works for your store alone and stays on your servers.
When do I need the API instead of Shopify Flow or Klaviyo?
When you build something of your own. Shopify Flow and Klaviyo react to subscription events without code: a flow tags a customer after a failed payment, a Klaviyo email goes out before each renewal. The API is for screens and systems you build yourself, such as an app where subscribers see their next delivery, or a back office that needs your subscriptions on demand.
How do I get access?
Both APIs are included in your plan. Tell the Zubs team which store it’s for and what you want to build, and we set up access. Your developers find the guides and a full API reference in the help center. When we change the API in a way that affects your integration, we tell you in advance.
Set it up in the help center: Zubs APIs.
Bottom line
Your subscriptions aren’t locked inside Shopify. Your developers can show them in your own app and systems, with sign-in through the Shopify customer account your subscribers already have.
Frequently asked questions
- Does the API cost extra?
- No. API access is included in your Zubs plan. Ask the Zubs team and we set it up for your store.
- Do I need a developer?
- Yes. The APIs are for your developers or your agency. For automations without code, use the Zubs triggers and actions in Shopify Flow.
- Do subscribers need a separate login for my app?
- No. They sign in with their Shopify customer account, the same email and one-time code as in your store.
- Can subscribers see each other's data through the customer API?
- No. A signed-in subscriber only reaches their own subscriptions. Every other request is turned away.
- Can I still use Shopify's own APIs?
- Yes. Subscriptions created with Zubs are Shopify subscription contracts, so Shopify's APIs and other apps still see them.