Shopify Admin

Shopify Admin API CLI for orders, products, customers, and store management. Uses REST and GraphQL APIs with environment-based authentication.

Security Scan

The skill is internally consistent: it is a simple CLI wrapper around Shopify Admin REST/GraphQL APIs and only requires the declared SHOPIFY_STORE_DOMAIN and SHOPIFY_ACCESS_TOKEN plus curl and jq.

Purpose & Capability

Name and description claim a Shopify Admin API helper; the included SKILL.md and shopify-admin.sh implement exactly that. Required binaries (curl, jq) and required env vars (SHOPIFY_STORE_DOMAIN, SHOPIFY_ACCESS_TOKEN) are appropriate and expected for this purpose.

Instruction Scope

Runtime instructions and the script only perform API calls to the Shopify store domain built from SHOPIFY_STORE_DOMAIN and use SHOPIFY_ACCESS_TOKEN. The SKILL.md explicitly states it does not source any files and the script honors that. No instructions reference other system files, unrelated env vars, or external endpoints.

Install Mechanism

No install spec (instruction-only plus an included script). Nothing is downloaded or written by an installer. This is a low-risk setup consistent with a small CLI helper.

Credentials

Only SHOPIFY_STORE_DOMAIN and SHOPIFY_ACCESS_TOKEN are required; these map directly to the Shopify Admin API usage. No additional unrelated credentials, config paths, or secret variables are requested.

Persistence & Privilege

always is false and the skill does not request elevated system presence or modify other skills/configuration. It can be invoked autonomously (platform default), which is normal for skills; this combined with the limited credential scope does not increase risk beyond expected behavior.

Assessment

This skill appears to do exactly what it says: run Shopify Admin API calls using the SHOPIFY_STORE_DOMAIN and SHOPIFY_ACCESS_TOKEN. Before installing, verify the token's scope (grant least privilege — read-only if you only need reads; avoid broad admin tokens if not necessary). Because the source/homepage is unknown, you may want to review the included shopify-admin.sh file (it is short and readable) and run the skill in an isolated environment or with a dedicated Shopify API token. Rotate the token if you later remove the skill, and ensure your gateway process does not expose other unrelated secrets to the same environment.

shopify-admin - Shopify Admin API

Interact with Shopify Admin API for order management, product operations, customer data, and store analytics.

Prerequisites

Required binaries: curl, jq (must be installed and on PATH).

Environment: The script uses only the process environment. It does not source any file (no ~/.openclaw/.env or other dotenv). Set these variables where the OpenClaw agent/gateway runs (e.g. export in shell, or in a file that your gateway loads at startup):

SHOPIFY_STORE_DOMAIN=your-store.myshopify.com
SHOPIFY_ACCESS_TOKEN=shpat_xxx

If the script is run by the agent, ensure the gateway process has these vars (many setups load ~/.openclaw/.env when starting the gateway — then the agent inherits them; the script itself does not read that file).

API Endpoints

REST API

Base URL: https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/

GraphQL API

Endpoint: https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/graphql.json

Common Operations

Orders

List orders:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/orders.json?status=any&limit=10" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" \
  -H "Content-Type: application/json"

Get specific order:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/orders/{order_id}.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Products

List products:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/products.json?limit=50" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Search products:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/products.json?title={title}" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Delete product:

curl -s -X DELETE "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/products/{product_id}.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Customers

List customers:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/customers.json?limit=50" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Get customer:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/customers/{customer_id}.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

GraphQL Queries

Get order with customer details:

curl -s -X POST "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/graphql.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query { order(id: \"gid://shopify/Order/{order_id}\") { id name customer { firstName lastName email } } }"
  }'

Marketing & Analytics

Marketing Events

List marketing events (campaigns, UTMs):

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/marketing_events.json?limit=50" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Get specific marketing event:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/marketing_events/{event_id}.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Create marketing event (track campaign):

curl -s -X POST "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/marketing_events.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "marketing_event": {
      "event_type": "ad",
      "utm_campaign": "spring_sale",
      "utm_source": "facebook",
      "utm_medium": "cpc",
      "started_at": "2026-01-15T00:00:00Z"
    }
  }'

Reports & Analytics

List available reports:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/reports.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Get report (sales, traffic, etc.):

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/reports/{report_id}.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Shop Analytics (Sessions, Traffic)

Get shop analytics/sessions data via GraphQL:

curl -s -X POST "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/graphql.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query { shop { name analytics { onlineStoreSessions { count } } } }"
  }'

Get online store sessions (REST):

# Note: Sessions data is typically available via Shopify Analytics API or Reports
curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/shop.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" | jq '.shop'

Order Attribution (UTM tracking)

Get order with attribution data:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/orders/{order_id}.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" | jq '.order | {id, name, referring_site, landing_site, source_name}'

List orders with UTM parameters:

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/orders.json?fields=id,name,referring_site,landing_site,source_name,created_at&limit=50" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Customer Events (Behavior tracking)

List customer events (visits, actions):

curl -s "https://$SHOPIFY_STORE_DOMAIN/admin/api/2026-01/customers/{customer_id}/events.json" \
  -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN"

Important Notes

PII Access Limitations

• Customer names, emails, addresses require Shopify plan or higher
• Basic plan: PII fields return null via API
• Web UI always shows full customer data
• Workaround: Use webhooks to capture PII before masking

API Versions

• Current: 2026-01
• Update version in URL for newer features

Rate Limits

• REST: 2 calls/second (Shopify plan)
• GraphQL: Same bucket as REST
• Check X-Shopify-Shop-Api-Call-Limit header

Response Codes

• 200: Success
• 201: Created
• 204: Deleted (no body)
• 429: Rate limited
• 403: Permission denied (check scopes)

Scopes Required

• read_orders, write_orders
• read_products, write_products
• read_customers, write_customers
• read_analytics
• read_marketing_events, write_marketing_events
• read_customer_events
• read_reports

Tips

• Use jq for JSON parsing: | jq '.orders[0]'
• Add -w "\nHTTP: %{http_code}" to curl for status codes
• Use GraphQL for complex nested queries
• REST is simpler for basic CRUD operations