# Shopify Plus & Headless Store Detector (`dataforge_api/shopify-plus-headless-stores-ppe`) Actor

Check a list of store domains: Shopify or not, headless (Hydrogen, Next.js) candidate, Plus indicators, myshopify handle, theme, currency, public emails and social links. Pay-per-event.

- **URL**: https://apify.com/dataforge_api/shopify-plus-headless-stores-ppe.md
- **Developed by:** [DataForge Lab](https://apify.com/dataforge_api) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.50 / 1,000 store domain analyseds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Shopify Plus & Headless Store Detector

Give a list of store domains and get back, for each one, whether it runs on Shopify, whether it looks headless (Hydrogen/Oxygen, Next.js or another JS framework in front of Shopify), how many Shopify Plus indicators it shows, its theme, currency, public emails and social links. One home page request per domain.

### Who uses it

- **Shopify agencies and app vendors** qualifying a prospect list: which stores are Plus-level, which are headless.
- **Ecommerce service providers** (checkout, CRO, subscriptions, headless tooling) filtering a list of stores before outreach.
- **Analysts** sizing the Shopify and headless share of a set of brands.

### What it does not do

It does not discover stores. No open directory of Shopify Plus stores exists, so you bring the domains (from your CRM, a lead list, or the `shopify-store-intel-ppe` discovery option).

### Input

```json
{
  "domains": ["allbirds.com", "gymshark.com", "rothys.com"],
  "onlyHeadless": false,
  "onlyPlusSignals": false,
  "includeNonShopify": false,
  "maxResults": 100
}
```

- `domains`: store domains or URLs.
- `onlyHeadless`: keep only stores that look headless.
- `onlyPlusSignals`: keep only stores with at least one Plus indicator.
- `includeNonShopify`: also save domains with no Shopify signal (they are charged like any other record).
- `maxResults`: cap on saved records.

### Output per store

`domain`, `final_url`, `is_shopify`, `is_headless_candidate`, `frameworks`, `hydrogen_oxygen`, `myshopify_domain`, `theme_name`, `theme_schema`, `theme_store_id`, `currency`, `locale`, `country`, `plus_signals`, `plus_likelihood`, `title`, `description`, `public_emails`, `social_links`.

### Honest limits

- Shopify does not publish which stores are on Plus. `plus_signals` (custom checkout domain, custom non-Theme-Store theme, Plus mentioned in the page) are heuristics, and `plus_likelihood` is not proof.
- Headless detection looks for Hydrogen/Oxygen or a JS framework in front of Shopify assets; some headless stores hide it.
- Only emails shown on the home page are returned.
- Sites that answer with HTTP 4xx/5xx (bot protection, rate limits) are reported in the log, not saved and not charged, because their platform cannot be determined.

### Pricing

Pay per event: `shopify-plus-headless-stores-record` $0.0045 per saved store domain.

# Actor input Schema

## `domains` (type: `array`):

Store domains or URLs to check, e.g. allbirds.com, gymshark.com. The Actor visits each home page once.

## `includeNonShopify` (type: `boolean`):

Also save domains where no Shopify or headless signal was found (they are charged like any other record).

## `onlyHeadless` (type: `boolean`):

Keep only stores that look headless (Hydrogen/Oxygen, or a JS framework in front of Shopify).

## `onlyPlusSignals` (type: `boolean`):

Keep only stores with at least one Shopify Plus indicator. Indicators are heuristics, not proof.

## `maxResults` (type: `integer`):

Maximum number of records to save.

## Actor input object example

```json
{
  "domains": [
    "allbirds.com",
    "gymshark.com",
    "rothys.com"
  ],
  "includeNonShopify": false,
  "onlyHeadless": false,
  "onlyPlusSignals": false,
  "maxResults": 100
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dataforge_api/shopify-plus-headless-stores-ppe").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("dataforge_api/shopify-plus-headless-stores-ppe").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call dataforge_api/shopify-plus-headless-stores-ppe --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dataforge_api/shopify-plus-headless-stores-ppe"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Xh0ZtcJxNRYsRqGog/builds/lHu9rmtpJIbWcuIpw/openapi.json
