# Tinder Email Scraper (`leads-scraper/tinder-email-scraper`) Actor

Tinder Email Scraper SD - Tinder Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Tinder results by keyword, location and email domain - Tinder email extractor.

- **URL**: https://apify.com/leads-scraper/tinder-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 4 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

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

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

### Tinder Email Scraper: public page email extraction from tinder.com

The Tinder Email Scraper is an Apify Actor that searches publicly indexed pages on `tinder.com` for email addresses and returns them as structured data. It runs Google `site:` queries, parses the search results, and writes each unique address to an Apify dataset.

**Read this before you run the Tinder Email Scraper.** Tinder does not publish indexable member profiles. There is no public directory of daters, and dating profiles are not crawlable by any tool, including this one.

Everything the Tinder Email Scraper can return therefore comes from Tinder's own public web surface: newsroom and press pages, editorial and blog content, help-centre articles, safety and careers pages, and brand or partnership pages. **Real-world yield is very low** — often a handful of addresses, sometimes zero.

Use the Tinder Email Scraper for what it honestly is: a narrow contact-discovery tool for publicly listed press, partnership and business addresses on one domain. If you want volume, the [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper), [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) and [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) are the right starting points instead.

#### Scope: what this Actor can and cannot do

| It can | It cannot |
|---|---|
| Find emails printed on publicly indexed `tinder.com` pages | Access dating profiles, matches or member data — none of it is public |
| Filter to email domains you choose, e.g. `@gmail.com` | Log in, use the Tinder API, or bypass any login |
| Return the page label and the exact query behind each lead | Read messages, swipes, photos or location data |
| Deduplicate every address across the whole run | Produce a list of daters — that data does not exist publicly |

There is no browser, no JavaScript rendering, no cookies and no authentication anywhere in the Tinder Email Scraper. All data collection happens against public Google search results, never against the Tinder app.

### Key features of the Tinder Email Scraper

| Feature | What it means in practice |
|---|---|
| Google `site:` targeting | Queries are scoped to `tinder.com` |
| Query expansion | Base, quoted and `intitle:` variants plus one variant per query modifier |
| Business-tuned modifiers | Ships with `email`, `contact`, `business` — the words that appear on press and partnership pages |
| Domain filtering | Only emails on your `customDomains` list are collected |
| Global deduplication | Each address is written once per run, across all queries and pages |
| Email normalisation | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Discards a hit that is only the tail of another email in the same block |
| Concurrency | An `asyncio` worker pool runs queries in parallel with a shared stop signal |
| Retry logic | Up to 3 attempts per page, exponential backoff, fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are retried, not treated as empty |
| Resumable state | Saved to the key-value store on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Fallback parser | A Google layout change degrades to "emails without page details", not zero results |

The engineering is solid, but engineering cannot invent data. On a domain with no public member pages, the Tinder Email Scraper is limited by what Tinder itself publishes. Base queries always run first, so the Tinder Email Scraper writes the most direct matches to your dataset before expanded variants begin.

### How the Tinder Email Scraper works

The pipeline has six stages:

1. It reads your input: keywords, location, email domains and limits.
2. It builds Google queries with the `site:` operator, for example `site:tinder.com press "@gmail.com" contact`.
3. It fetches Google result pages through the Apify **GOOGLE\_SERP** proxy using async `aiohttp` requests.
4. It parses each result block structurally — locating the `<h3>` title, then the smallest surrounding block — rather than depending on Google's CSS class names.
5. It extracts emails from the block text with a domain-filtered regular expression.
6. It deduplicates globally and pushes each lead into the Apify dataset immediately.

Because it reads search results rather than the site, the Tinder Email Scraper is not a browser-based crawler. Pagination means walking Google's result pages up to your page cap.

### Input fields

Input to the Tinder Email Scraper is plain JSON. Only `keywords` is required.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["coach", "creator"]` | Search terms describing the pages you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com","@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional |
| `maxEmails` | integer 1-10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email","contact","business"]` | Extra words combined with each keyword |
| `maxPagesPerQuery` | integer 1-50 | `30` | Pagination cap per query |
| `maxConcurrency` | integer 1-20 | `5` | Parallel queries |

On this domain, the keywords that actually work with the Tinder Email Scraper are editorial and corporate: `press`, `media`, `partnership`, `newsroom`, `careers`, `safety`. Person-style keywords will not find people, because Tinder publishes none.

#### JSON input example for the Tinder Email Scraper

```json
{
  "keywords": ["press", "partnership", "media inquiries"],
  "location": "",
  "customDomains": ["@gmail.com", "@tinder.com"],
  "maxEmails": 20,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

Adding `@tinder.com` to `customDomains` is often the only way a Tinder Email Scraper run returns anything at all, since a corporate press address on a corporate page is the realistic target.

### Output schema and dataset

Every dataset item the Tinder Email Scraper writes carries the same 14 fields, so the output schema stays consistent even when the run is small.

| Field | Meaning |
|---|---|
| `network` | Platform name — always `Tinder` |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account or page label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for page titles |
| `username` | URL-safe handle when one is exposed; otherwise `null` |
| `profileUrl` | Canonical account URL when a handle is known; otherwise empty |
| `url` | Direct page link when exposed, else the profile URL |
| `description` | Snippet text, cleaned of labels and counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, e.g. `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

#### Example output record

An honest example of a Tinder Email Scraper result. It is a corporate press contact from a public page — `username` is `null` and `profileUrl` is empty, because there is no member handle behind it.

```json
{
  "network": "Tinder",
  "keyword": "press",
  "query": "site:tinder.com press \"@tinder.com\" contact",
  "title": "Newsroom - Media Resources | Tinder",
  "accountName": "Tinder Newsroom",
  "fullName": "",
  "username": null,
  "profileUrl": "",
  "url": "https://tinder.com/newsroom",
  "description": "For media inquiries and interview requests, contact press@tinder.com.",
  "email": "press@tinder.com",
  "emailDomain": "@tinder.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T12:41:33.905Z"
}
```

Expect most Tinder Email Scraper runs to look like this: a small number of corporate, press or partnership addresses, with empty handle fields throughout.

Export the Tinder Email Scraper dataset as JSON, CSV, Excel or XML, or read the structured data over the Apify API.

### Use cases for the Tinder Email Scraper

| Use case | How the Tinder Email Scraper helps |
|---|---|
| PR and media outreach | Finds publicly listed press and newsroom addresses on `tinder.com` |
| Partnership and BD research | Surfaces business or partnership contacts published on public pages |
| Brand-safety and compliance audits | Records which contact addresses the domain exposes publicly |
| Competitive monitoring | Builds a structured dataset of Tinder's public contact surface over time |
| Domain contact discovery | A quick, scoped check of what emails one domain publishes |

There is no legitimate dating-outreach use case here, and the Tinder Email Scraper cannot support one. For dating-adjacent creator and coach outreach, use the [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) or [YouTube Email Scraper](https://apify.com/leads-scraper/youtube-email-scraper), where those creators actually publish contact details.

### Tips for better results

Four adjustments give the Tinder Email Scraper its best shot on a thin domain.

Use corporate vocabulary. `press`, `newsroom`, `media`, `partnership` and `careers` reflect what is genuinely indexed on this domain.

Add `@tinder.com` and `@matchgroup.com` to `customDomains`. Free-mail addresses are rare on a corporate site, so the default domain list often gives the Tinder Email Scraper nothing to match.

Keep `expandQueries` on. Google caps a single query at roughly 300 results, and query expansion is how the Tinder Email Scraper widens a very thin search surface.

Set `maxEmails` low, such as 10 or 20. Raising it will not create leads that do not exist, and a low cap keeps the run short and cheap.

### Limitations of the Tinder Email Scraper

Read this section carefully — it is the most important part of this page.

- **Tinder does not publish indexable member profiles.** The Tinder Email Scraper finds contacts only on public marketing, blog, editorial and help pages, so real-world yield is very low and can legitimately be zero.
- It **cannot** produce dating-profile contact details. That data is not public and is not accessible to this or any other Actor.
- Only emails already **publicly visible in Google's index** can be found.
- Google caps a single query at roughly **300 results**, which is exactly why query expansion exists.
- `username` and `profileUrl` are almost always empty here, because corporate pages expose no handle. That is a Google and platform limitation, not a bug.
- `possiblyTruncated: true` means Google's snippet ellipsis may have cut the address — verify before sending.
- The Tinder Email Scraper **requires the Apify GOOGLE\_SERP proxy** and cannot run without Apify proxy credentials.
- Free Apify plans are capped at **100 emails per run**; paid plans are uncapped. On this platform that cap will rarely be reached.
- Results vary with keywords, domains and location. No volume is guaranteed.

### Related Actors

Every Actor below runs the same engine as the Tinder Email Scraper against a different platform. The social and creator platforms near the top of this table have far larger public indexes and are much better starting points.

| Actor | What it collects |
|---|---|
| [Tinder Email and Phone Number Scraper](https://apify.com/leads-scraper/tinder-email-and-phone-number-scraper) | Emails and phone numbers from Tinder |
| [Tinder Phone Number Scraper](https://apify.com/leads-scraper/tinder-phone-number-scraper) | Public phone numbers from Tinder |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### FAQ

#### How many results should I expect from the Tinder Email Scraper?

Very few. Because Tinder publishes no indexable member profiles, a typical run returns a handful of corporate or press addresses at best, and zero is a normal outcome for a narrow keyword set. Do not budget a campaign around this Actor's volume.

#### Does the Tinder Email Scraper access private, member-only or dating-profile data?

No. It never logs in, never touches the Tinder API and never opens the app. It reads publicly indexed Google search results only. Dating profiles, matches, messages, photos and location data are entirely out of reach and always will be.

#### Can the Tinder Email Scraper find someone's email from their Tinder profile?

No. Tinder profiles are not public, are not indexed, and do not contain email addresses. Any tool claiming otherwise is misrepresenting what is possible.

#### What does the Tinder Email Scraper actually find, then?

Publicly listed contacts on `tinder.com` — press and newsroom addresses, partnership or business inquiry addresses, and anything printed openly in help, careers or editorial pages.

#### Which domain does the Tinder Email Scraper search?

`tinder.com`, and only that domain.

#### Why are `username` and `profileUrl` almost always empty?

Because corporate and editorial pages expose no account handle to Google. The Tinder Email Scraper records `accountName` and leaves the handle fields empty rather than inventing one.

#### Does the Tinder Email Scraper need a proxy?

Yes. The Apify GOOGLE\_SERP proxy is required; without Apify proxy credentials no search results can be fetched.

#### What does `possiblyTruncated` mean?

Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before contacting anyone.

#### Can I resume an interrupted Tinder Email Scraper run?

Yes. Progress is stored in the key-value store, keyed by a hash of your input, and survives migrations and aborts.

#### Which Actor should I use instead for real volume?

[Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper), [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) or [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper). All three sit on far larger public indexes.

#### Is this affiliated with Tinder or Match Group?

No. The Tinder Email Scraper is an independent Apify Actor with no affiliation, endorsement or official relationship with Tinder or Match Group.

#### Are the collected emails verified?

No. The Tinder Email Scraper performs contact discovery, not deliverability verification. Run the export through your own verification step, and follow the rules that apply to your outreach.

### Leave a review

If the Tinder Email Scraper saved you time, please leave a star rating and a short review on
the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions about the Tinder Email Scraper, bug reports or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Tinder accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Tinder.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "coach",
    "creator"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "business"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Tinder Email Scraper, stored in the run's default dataset.

# 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 = {
    "keywords": [
        "coach",
        "creator"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/tinder-email-scraper").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 = {
    "keywords": [
        "coach",
        "creator",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/tinder-email-scraper").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 '{
  "keywords": [
    "coach",
    "creator"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "business"
  ]
}' |
apify call leads-scraper/tinder-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/tinder-email-scraper"
        }
    }
}
```

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/Aic321KY3gY1tgfNf/builds/FyVriNNbxvdCFeg5k/openapi.json