Connecting SHOPLINE to an AI agent: two auth modes, real reads, approval-gated writes
SHOPLINE is now a first-class connected platform. You can connect through the registered OAuth app or by pasting a private-app Admin token, the agent reads products, orders and a real sales summary, and any store change it proposes waits for your approval. One important scoping note up front: this covers International SHOPLINE, not the TW/HK platform, which is a different API.
Which SHOPLINE this covers
This integration targets International SHOPLINE — stores on `{handle}.myshopline.com`, documented at developer.shopline.com. The Taiwan/Hong Kong platform on `*.shoplineapp.com` is a genuinely different API and is not covered. Worth checking which one you're on before you plan around it, because the domains look similar enough to assume.
Two ways to connect
| Mode | How it works | Token lifetime |
|---|---|---|
| Registered OAuth app | Standard OAuth flow through the SHOPLINE app | ~10 hours, refreshed automatically |
| Private-app Admin token | You generate a token in your store and paste it | ~3 years, never refreshed by us |
What the agent can read
- Store info — the shop's own configuration and identity.
- Products — catalogue with filtering, including what's live versus not.
- Orders — order-level data, which is what makes real revenue analysis possible.
- An exact sales summary — computed server-side rather than approximated from a page of orders.
- Anomaly detection — the same statistical detector used across the other platforms, so an unusual sales pattern surfaces without you defining a rule for it.
- A generic admin read for anything the named tools don't cover.
Writes, and the gate on them
Store changes route through a single approval-gated write gateway. The agent proposes the change, shows exactly what would apply, and nothing reaches the store until you approve it — the same path used for a Google Ads budget change, not a looser one because it's commerce.
There's also a deliberate guard against cross-platform confusion: a Shopify-shaped call won't be silently applied to a SHOPLINE store or vice versa. The two platforms are similar enough that this class of mistake is easy to make and expensive to discover.
Why connect a store at all
Because platform-reported conversion value is not profit. Reconciling ad spend against actual settled orders — after refunds, returns and discounts — is the difference between a ROAS dashboard and a number you'd defend in a budget meeting. That's covered in depth in optimizing on profit instead of ROAS, and the practical walkthrough is in SHOPLINE store analysis.
Frequently asked questions
- Does Agent Planners support SHOPLINE?
- Yes — International SHOPLINE (stores on {handle}.myshopline.com) is natively supported, covering store info, products, orders, an exact sales summary and anomaly detection, plus approval-gated store writes.
- Does it work with SHOPLINE Taiwan or Hong Kong?
- No. The TW/HK platform on *.shoplineapp.com is a different API and is not covered by this integration. Check which platform your store is on before planning around it.
- How do I connect without an app review?
- Use the private-app path — generate an Admin token in your store and paste it. Those tokens last around three years and are not refreshed by us, unlike the OAuth app's ~10-hour tokens which refresh automatically.
- Can the agent change my SHOPLINE store?
- Only with your approval. Writes route through a single approval-gated gateway that shows exactly what would apply before anything reaches the store.
- What stops a Shopify command being applied to my SHOPLINE store?
- An explicit cross-platform confusion guard. The two are similar enough that a mistaken call is easy to make, so the integration refuses rather than silently applying it to the wrong platform.