# Apple App Store · Developer Emails (`corent1robert/apple-app-store-developer-contacts`) Actor

Export unique iOS App Store publishers for partnership and outreach. Seller website, App Store profile and app portfolio — one publisher per row, not per listing. Keyword, app URL, or genre charts. Optional website email enrich. No login. No API key

- **URL**: https://apify.com/corent1robert/apple-app-store-developer-contacts.md
- **Developed by:** [Corentin Robert](https://apify.com/corent1robert) (community)
- **Categories:** Lead generation, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.15 / 1,000 unique app store publishers

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Apple App Store · Unique Developer Contacts

Export **unique iOS App Store publishers** for partnership and outreach — seller website, App Store developer page, and app portfolio. **One publisher per row**, not one row per listing.

**No login. No API key. No Apple developer account.**

> **Unit of work:** 1 unique `artistId` (seller). Two apps from the same company count as **one** charged row.

***

### Who is this for?

| You are… | Typical goal | Suggested setup |
|----------|--------------|-----------------|
| Mobile SaaS / SDK vendor | Prospect iOS publishers in a niche | **Search** + keyword (`invoice`, `crm`, `fitness`) |
| ASO / growth agency | Build an outreach list from a category | **Charts** + genre (Business, Productivity…) |
| Partnership / BD | Refresh one known competitor’s publisher | Paste an **App Store URL** |
| Outbound / SDR | Need inboxes, not only websites | Turn **Enrich email from website** ON |

**What you get by default:** publisher name, `artistId`, App Store developer page, seller website when Apple publishes it (~70%+ on keyword pools), sample app + ratings, genres, portfolio size in the run.

**When to enable enrichment:** turn **Enrich email from website** ON when you need a public mailbox scraped from the seller site. Off by default (faster, higher fill on website-only rows).

***

### Modes

1. **Search** — keyword or App Store / iTunes URL (or bare numeric app id).
2. **Charts** — Top Free / Paid / Grossing for a **genre** + country (classic iTunes RSS → lookup).
3. **App URL** — automatic when you paste `https://apps.apple.com/…/id…` (loads that publisher’s portfolio).

There is **no full-catalog dump** in v1 (Apple search is capped ~200 results per query and does not paginate). Use keywords + genre charts to cover your ICP.

***

### What it extracts

| Field | Notes |
|-------|--------|
| `developerName` / `artistId` | Seller identity + stable dedupe key |
| `developerWebsite` / `developerDomain` | From `sellerUrl` (origin only) |
| `developerProfileUrl` | apps.apple.com developer page |
| `developerEmail` | Only if enrich is ON and a public inbox is found |
| `appCount`, `appNames`, `maxRatingCount` | Portfolio signal in this run |
| `sampleApp*` / `listingUrl` | Strongest app in the pool (by ratings) |
| `genres`, `countries`, `discoverySources` | Context for CRM / research |

Apple **does not** publish a support email on the store listing API. Do not scrape App Store HTML for emails — pages mix related apps. Enrichment only uses the **seller website**.

***

### Input (Console)

| Field | Default | Role |
|-------|---------|------|
| Mode | Search | Search vs Charts |
| Keyword or App Store URL | `invoice` | Search / URL |
| Genre | None | Required for Charts |
| Chart type | Top Free | Charts only |
| Country | `us` | Storefront |
| Max unique developers | 20 | Cap |
| Minimum ratings | 0 | Quality floor |
| Require website | No | Contactability |
| Enrich email from website | **No** | Optional crawl |
| Require email | No | Use with enrich |
| Exclude consumer inboxes | No | Gmail/Yahoo/… |

**API-only (optional):** `proxyConfiguration`, `minDelayMs`, `maxRequestRetries`, `maxEmailLookups`, `verboseLogs`.

***

### Pricing

Pay-per-event: **unique publisher** written to the dataset — **$4.50 / 1,000** on Free (`$0.0045` / row → Diamond `$0.00225`).

Competing “1 lead per app” Actors often charge **$0.01–$0.05 per app**. Unique-publisher billing stays cheaper when the same seller has many titles.

***

### Local development

```bash
cd apple-app-store-developer-contacts
npm install
npm test
npm run start:dev
```

***

### Internals (developers)

- HTTP-only via iTunes Search / Lookup + classic RSS charts (`got-scraping`).
- Search hard wall ~200 results/query; `offset` does not paginate — design assumes keyword + chart shards.
- Optional website enrich: homepage + a few contact-ish same-origin links; noise filters for asset false positives.

***

### Support

corentin@outreacher.fr

# Actor input Schema

## `mode` (type: `string`):

**Search (default):** keyword or App Store URL in Step 2.

**Charts:** pick a genre (and chart type) — top apps in that category become unique publishers.

Paste an app URL anytime — the Actor switches to App URL lookup automatically.

## `query` (type: `string`):

Examples: `invoice` · `crm` · `https://apps.apple.com/us/app/notion-notes-tasks-ai/id1232780281`

A full app URL loads that publisher’s portfolio. **Ignored** when Mode is Charts (unless you leave genre empty by mistake).

## `genre` (type: `string`):

Required for **Charts**. Optional otherwise. No genres are excluded — pick what matches your ICP.

## `chartType` (type: `string`):

Used in **Charts** mode. Free / Paid / Grossing leaderboards for the selected genre.

## `country` (type: `string`):

Two-letter App Store country (US, FR, GB, DE…). Default **US**.

## `maxDevelopers` (type: `integer`):

**Global** cap of unique publisher rows (one seller, many apps). Default **20** keeps first runs cheap. Up to **2,000**.

## `minRatingCount` (type: `integer`):

Keep publishers whose strongest app in the pool has at least this many ratings. **0** = no floor.

## `requireWebsite` (type: `string`):

**No (default):** keep publishers even without a public seller website. **Yes:** only rows with a website.

## `enrichEmails` (type: `string`):

**No (default):** export website + App Store profile only. **Yes:** visit seller websites and harvest a public contact email when found (slower).

## `requireEmail` (type: `string`):

**No (default):** keep publishers without an email. **Yes:** only rows with an email (turn Enrich on, or you will get few/no rows).

## `excludeGmail` (type: `string`):

**No (default):** keep Gmail / Yahoo / Outlook / iCloud. **Yes:** skip consumer inboxes when an email is present.

## `chartLimit` (type: `integer`):

How many chart apps to pull in Charts mode (before unique-publisher merge). Default **100**, max **200**.

## `verboseLogs` (type: `boolean`):

Extra debug lines in the run log (for support).

## Actor input object example

```json
{
  "mode": "search",
  "query": "invoice",
  "genre": "",
  "chartType": "free",
  "country": "us",
  "maxDevelopers": 20,
  "minRatingCount": 0,
  "requireWebsite": "no",
  "enrichEmails": "no",
  "requireEmail": "no",
  "excludeGmail": "no",
  "chartLimit": 100,
  "verboseLogs": false
}
```

# Actor output Schema

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

Who to contact: name, website, app count, sample listing

## `outreachCrm` (type: `string`):

Email, website and App Store profile for a first email

## `marketResearch` (type: `string`):

Ratings, portfolio size and genres

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

All publisher rows

## `output` (type: `string`):

Publishers scraped, apps scanned, filters

## `runLog` (type: `string`):

Live progress

# 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 = {
    "query": "invoice",
    "country": "us"
};

// Run the Actor and wait for it to finish
const run = await client.actor("corent1robert/apple-app-store-developer-contacts").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 = {
    "query": "invoice",
    "country": "us",
}

# Run the Actor and wait for it to finish
run = client.actor("corent1robert/apple-app-store-developer-contacts").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 '{
  "query": "invoice",
  "country": "us"
}' |
apify call corent1robert/apple-app-store-developer-contacts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,corent1robert/apple-app-store-developer-contacts"
        }
    }
}

```

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/3TfadKatz9TLeFU1a/builds/Es4pjL4FcvmC4U4wk/openapi.json