# Tinder Phone Number Scraper - Keyword Search, Verified Numbers (`scrapido/tinder-phone-number-scraper`) Actor

📞 Tinder Phone Number Scraper searches by keyword and location and returns validated numbers. ✅ Country code, line type and carrier on every record. 📊 Useful for dating market research & trend analysis teams.

- **URL**: https://apify.com/scrapido/tinder-phone-number-scraper.md
- **Developed by:** [Scrapido](https://apify.com/scrapido) (community)
- **Categories:** Lead generation, Automation, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 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.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

### Tinder Phone Number Scraper 📱

**Tinder Phone Number Scraper** is an Apify automation actor that saves you from time-consuming manual research when you need phone number discovery from Tinder profiles, bios, and post content. It streamlines tinder number scraping for marketers and researchers, using a **tinder phone number scraper** approach with keyword-led lead generation and country targeting—so you can build outreach lists faster with measurable ROI.

***

### What is Tinder Phone Number Scraper? 🔍

**Tinder Phone Number Scraper** is an Apify actor built to extract phone numbers from Tinder using your chosen keywords and country targeting. It works like a **Tinder email extractor**, but for phone numbers—so teams doing automated Tinder scraping can quickly collect leads for analysis, outreach, or operational research. Whether you’re a sales professional, recruiter, or marketer, this **tinder phone number scraper** helps you find contacts by pairing your interest terms with the correct dial code. You can use it as a **tinder contact scraper** for focused runs or as part of a broader pipeline for tinder data scraping.

***

### What Does Tinder Phone Number Scraper Do? ⚙️

This actor takes your input (keywords, optional location, and the country dial code), then scrapes phone numbers from Tinder profile and content pages, and finally exports the results into your Apify dataset in a consistent JSON record format—ideal for downstream analysis.

Capabilities:

- 🔍 **Scrapes** Tinder profiles and post content using your provided keywords and filters
- 📞 **Extracts** phone numbers from publicly available content associated with Tinder profiles
- 🌍 **Targets** results by country (dial code) and can optionally narrow by location
- 🧾 **Normalizes & structures** each match into clean dataset records
- 📊 **Exports** results to the Apify dataset so you can filter, enrich, and use them in your workflow

***

### What Would Results from Tinder Phone Number Scraper Look Like? 👀

You’ll receive one JSON record per found phone number, including the originating keyword, profile details, and country formatting.

```json
{
  "keyword": "founder",
  "title": "Alexandra Smith",
  "description": "Austin, TX | Founder & community builder | WhatsApp available +1-555-014-2273",
  "url": "https://tinder.com/@alexandra_smith",
  "phone_number": "+15550142273",
  "country": "United States",
  "dial_code": "+1"
}
```

Export from the **Dataset** tab as JSON or CSV (via Apify’s dataset tools).

***

### Capabilities of Tinder Phone Number Scraper 🛠️

| Capability | What It Means for You |
|---|---|
| ✅ **Keyword Search** | Target Tinder leads that match your exact keyword set for the audience you care about |
| ✅ **Location Filter** | Optionally focus scraping on a city, region, or country context to improve relevance |
| ✅ **Country Targeting (Dial Code)** | Choose the country to target for phone numbers to support cleaner lead generation via scraping |
| ✅ **Result Cap (`maxPhoneNumbers`)** | Stop after you’ve gathered enough numbers; higher limits can increase run duration |
| ✅ **Resume Support** | If a run is interrupted, it resumes using saved progress so you don’t lose work |
| ✅ **Real-Time Dataset Writes** | Each result is pushed to the dataset incrementally while scraping proceeds |
| ✅ **Proxy Support for Reliability** | Built-in proxy support helps keep large scraping jobs stable |
| ✅ **Structured Dataset Output** | Returns consistent records with phone number formatting fields for easier analysis |
| ✅ **Built for Bulk Data Workflows** | Ideal for OSINT phone number discovery, research, and data harvesting tools pipelines |

***

### Launch Your First Tinder Phone Number Scraper Task 🚀

#### Required Input Fields

```json
{
  "keywords": ["marketing", "founder"],
  "location": "",
  "country": "United Kingdom (+44)",
  "maxPhoneNumbers": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---:|---|---|
| `keywords` | array | ✅ Yes | `["marketing","founder"]` | Enter keyword terms to search for Tinder profiles and content related to your outreach or research audience. |
| `location` | string | No | `""` | Filter by location (for example, `London` or `California`). Leave empty for global targeting. |
| `country` | string | ✅ Yes | `"United Kingdom (+44)"` | Select the country whose dial code you want to target for phone numbers. |
| `maxPhoneNumbers` | integer | No | `20` | Stop scraping after this many phone numbers are found. A higher limit may extend the scraping duration. |

#### Required Output Fields

| Field | Type | Description |
|---|---|---|
| `keyword` | text | The keyword that led to this particular result. |
| `title` | text | The Tinder profile or business title captured with the match. |
| `description` | text | The profile or content text associated with the found phone number. |
| `url` | link | The Tinder URL for the matched profile. |
| `phone_number` | text | The extracted phone number for this record. |
| `country` | text | The country label used for the match. |
| `dial_code` | text | The dial code associated with the selected country targeting. |

**Step-by-step launch guide:**

1. **Open** the actor in Apify and go to the **Input** tab
2. **Add your keywords** (start with 2–5 terms for a focused tinder contact extraction run)
3. **Pick a country** to target the right dial code
4. **Optionally add a location** to improve relevance for tinder number scraping
5. **Set `maxPhoneNumbers`** (use the default `20` to test, then raise it for bulk collection)
6. **Click Start** and watch the live run logs
7. **Download your dataset** from the Dataset tab for CRM import or further analysis

***

### Solving Real Problems with Tinder Phone Number Scraper 💼

- 🎯 **Lead generation via scraping** — find phone contacts faster than manual mobile app web scraping
- 📣 **Campaign targeting** — build country-segmented contact batches for outreach and testing
- 🔬 **Competitive research** — map contact patterns and communication claims visible in Tinder bios and posts
- ⚙️ **Automated pipelines** — schedule recurring OSINT phone number discovery jobs via Apify workflows
- 🧠 **Data harvesting tools** — structure results into a consistent dataset for analytics and enrichment

***

### What Sets Tinder Phone Number Scraper Apart? 🏆

- 🎯 **Focused targeting** with country dial-code selection to improve the usefulness of each match for phone number discovery
- 🔁 **Resume-friendly runs** so long jobs don’t start over from scratch
- 📈 **Dataset-ready structure** with clean fields (keyword, url, phone\_number, country, dial\_code) for easy downstream processing
- 🤝 **Human support** for custom scraping needs—email <scrapidocontact@gmail.com>

***

### Search Limits and Capacity 📈

Use `maxPhoneNumbers` to control run duration and cost exposure. By default, the actor caps extraction at **20** phone numbers per run. Result volume depends on how many Tinder profiles and bios/post content include publicly available phone numbers matching your keywords and country targeting. For larger runs, you can raise the cap and rely on proxy support for more reliable scraping browser automation.

***

### Is It Legal to Scrape Tinder? ⚖️

This actor works with **publicly available data** from Tinder. It does not access private profiles or restricted content. Users are responsible for complying with applicable privacy laws, platform policies, and anti-spam rules, including GDPR data protection requirements where relevant. If you need compliance guidance or want to request data removal, contact <scrapidocontact@gmail.com>.

***

### Ending Note ✉️

Stop spending hours manually hunting for contacts. **Tinder Phone Number Scraper** delivers structured, dataset-ready phone number results using your keywords and country targeting—so you can move from discovery to outreach (or analysis) with far less effort.

***

### FAQ — Tinder Phone Number Scraper ❓

#### How Does the Tinder Phone Number Scraper Work?

You provide `keywords`, a `country`, and optionally a `location` and `maxPhoneNumbers`. The actor then scrapes Tinder pages for phone numbers matching your targeting and saves each found result as a record in the Apify dataset.

#### What Types of Tinder Profiles Can I Target?

The actor is designed to extract phone numbers from Tinder profiles and from publicly visible Tinder bios and post content. Results typically reflect what’s publicly stated in those areas.

#### How Did the Tinder Phone Number Scraper Perform in Our Tests?

Performance depends on your keyword set, selected country targeting, and how often public Tinder profile content includes phone numbers. If results are fewer than expected, try broader keywords or adjust the country setting.

#### Why Scrape Tinder Instead of Buying a List?

Scraping publicly available content can produce fresher, more niche-specific results than many purchased datasets. You also retain control over keywords and country targeting, which improves lead generation via scraping compared to one-size-fits-all contact lists.

#### How Much Does Tinder Phone Number Scraper Cost?

Cost is determined by Apify run billing and the amount of data collected per run. To manage volume, use `maxPhoneNumbers` as your cap for each execution.

#### Top Benefits of the Tinder Phone Number Scraper

The main benefits are faster phone number discovery, consistent structured output in your dataset, and control over relevance through keywords and country targeting—making tinder data scraping easier to use in lead generation via scraping workflows.

#### What Are the Disadvantages of Scraping Tinder?

Not every profile includes a publicly visible phone number. Yield varies based on the visibility of phone numbers in profile bios and post content and the relevance of your keywords. Broader keywords and different country targeting can help when results are low.

#### How to Choose the Best Tinder Scraper

Choose based on how well the actor supports your targeting needs (keywords + country + optional location), how reliably it writes results into a dataset, and how easy it is to export structured records for your pipeline. If you have custom OSINT phone number use cases, contact <scrapidocontact@gmail.com>.

***

### 🆘 Support & Feedback

Have a question or want to propose improvements for **Tinder Phone Number Scraper**?

Please contact <scrapidocontact@gmail.com>.

### Multiple Phone Type

**Phone Types** replaces the old single Number Type choice: select as many kinds
of line as you want and the run collects all of them.

| Type | Kept when the number is |
| --- | --- |
| Mobile | A confirmed mobile |
| Landline | A confirmed fixed line |
| Toll-Free | A freephone number |
| VoIP | An internet-telephony number |
| Premium-Rate | A premium-rate number |
| Shared-Cost | A shared-cost number |

Leave it empty for every type. Each number is checked against its *real* line
type before being kept, so the filter is enforced rather than merely requested.
Numbers on ranges where mobile and landline genuinely cannot be told apart (the
US, Canada and Mexico) are kept rather than silently dropped - discarding them
would quietly lose good leads.

### Outreach links

| Field | Meaning |
| --- | --- |
| `telLink` | A clickable `tel:` link, so a row can be dialled straight from a spreadsheet or CRM |
| `whatsappLink` | A `wa.me` chat link, or empty for a confirmed landline or a number that failed validation |
| `whatsappCapable` | Whether the number is on a line WhatsApp can run on |

`whatsappCapable` is a plain yes/no you can filter on. It never claims the
person actually uses WhatsApp - only that the number is of a kind that could.
Switch the links off with **Include WhatsApp links**; the capability flag is
still reported.

# Actor input Schema

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

Enter keywords to search for (e.g., 'Target Keyword').

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

Filter by location (e.g., 'London', 'California'). Leave empty for global search.

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

Select the country to target for phone numbers.

## `maxPhoneNumbers` (type: `integer`):

Stop scraping after this many phone numbers are found. Setting a higher limit extends the scraping duration.

## `numberType` (type: `string`):

Restrict results to a specific line type, classified offline via libphonenumber. Any keeps every valid match.

## `phoneTypes` (type: `array`):

Which kinds of line to collect. Pick as many as you like - each number is checked against its real line type before it is kept. Leave empty for every type. Numbers on ranges where mobile and landline cannot be told apart (the US, Canada and Mexico) are always kept rather than silently dropped.

## `includeWhatsappLinks` (type: `boolean`):

Add a ready-made wa.me chat link for numbers on a line WhatsApp can run on. The link means the number is in a form WhatsApp accepts - not proof that an account exists.

## Actor input object example

```json
{
  "keywords": [
    "contact",
    "coach"
  ],
  "country": "United States (+1)",
  "maxPhoneNumbers": 20,
  "numberType": "Any",
  "phoneTypes": [
    "Mobile"
  ],
  "includeWhatsappLinks": true
}
```

# Actor output Schema

## `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 = {
    "keywords": [
        "contact",
        "coach"
    ],
    "phoneTypes": [
        "Mobile"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapido/tinder-phone-number-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": [
        "contact",
        "coach",
    ],
    "phoneTypes": ["Mobile"],
}

# Run the Actor and wait for it to finish
run = client.actor("scrapido/tinder-phone-number-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": [
    "contact",
    "coach"
  ],
  "phoneTypes": [
    "Mobile"
  ]
}' |
apify call scrapido/tinder-phone-number-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapido/tinder-phone-number-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/LQi2CpXFREi71pup2/builds/cV9CbfqILSCKt7zVp/openapi.json