# Páginas Amarelas / pai.pt Scraper (`memo23/paginasamarelas-scraper`) Actor

Scrape pai.pt (Páginas Amarelas Portugal) into structured business rows: name, phone, email when listed, website, address, hours. Keyword plus city, nationwide PT, or a search/profile URL. JSON or CSV out. $5 per 1,000 listings.

- **URL**: https://apify.com/memo23/paginasamarelas-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** Lead generation
- **Stats:** 17 total users, 17 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

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

## Páginas Amarelas / pai.pt Scraper

Scrape [pai.pt](https://www.pai.pt/) (Páginas Amarelas Portugal) into one row per **business**: name, phone, email when listed, website, address, opening hours.

Works from a keyword plus optional city, a nationwide term, or a pasted `/searches` or `/paginas/{id}` URL. Search cards and profile JSON-LD answer without Apify Proxy.

**Pricing:** $0.005 per listing (`pushData`). Extra `contact-phone` $0.002 and `contact-email` $0.05 when those fields are present.

### Why use this scraper?

- Phone, address, category, and hours sit on the search card.
- Profile pages add email (mailto), coordinates, and the business website when Páginas Amarelas publishes them.
- Nationwide query or a city resolved through `/location_suggestions`.
- Optional harvest of the business site when the directory has no inbox.

### Overview

Built for lead lists and local research on Portuguese companies. Each dataset item is one listing from pai.pt. `paginasamarelas.pt` redirects to the same host and is accepted as a start URL.

### Supported inputs

| Input | What it does |
|---|---|
| `searchTerms` | What you type in Páginas Amarelas, e.g. `restaurante`, `canalizador` |
| `locations` | City resolved via location suggestions. Empty = nationwide |
| `startUrls` | `https://www.pai.pt/searches?...` or `/paginas/{id}-{slug}` |
| `maxItems` | Stop after N unique listings (free plan cap 50) |
| `harvestWebsiteEmail` | Fetch the business site if pai.pt has no inbox |
| `proxy` | Leave off |

Unsupported: Páginas Amarelas Spain (`paginasamarillas.es` — that is a different actor), Ireland Golden Pages, sales-only `/empresas` pages.

### Use cases

| Who | Why |
|---|---|
| Sales / agencies | Portuguese phones and emails from a category |
| Researchers | Hours, city, and postcode coverage |
| SEO / maps | Website + coordinates per listing |

### How it works

1. Build `https://www.pai.pt/searches?search[query]={term}` (city + `location_id` when set). Page N is `&page=N`.
2. Parse `.card.card--result` for name, phone, address, hours (`data-schedule`).
3. Open `/paginas/{id}-{slug}` for LocalBusiness JSON-LD, mailto, and website.
4. Charge `contact-phone` / `contact-email` after `pushData`.
5. If still no email and harvest is on, fetch the business homepage/contact page.

### Input configuration

| Field | Type | Required | Notes |
|---|---|---|---|
| `searchTerms` | string\[] | one of terms/URLs | e.g. `restaurante` |
| `locations` | string\[] | no | e.g. `Lisboa` |
| `startUrls` | url\[] | no | `/searches` or `/paginas/` |
| `maxItems` | integer | no | default 50 |
| `maxPages` | integer | no | default 20 |
| `scrapeDetails` | boolean | no | default true |
| `harvestWebsiteEmail` | boolean | no | default true |
| `maxConcurrency` | integer | no | default 5 |
| `proxy` | proxy | no | default off |

#### Example input

```json
{
  "searchTerms": ["restaurante"],
  "locations": ["Lisboa"],
  "maxItems": 10,
  "harvestWebsiteEmail": false,
  "proxy": { "useApifyProxy": false }
}
```

### Output overview

One JSON object per business. Search cards already carry phone, address, category, and hours. Profile pages add email and coordinates when present.

### Output samples

`restaurante` in Lisboa, profile merge (fields trimmed):

```json
{
  "listingId": "428034",
  "name": "Restaurante Sashimi",
  "phone": "965557446",
  "email": "restsashimi@gmail.com",
  "street": "Rua Teresa Jesus Pereira 35B",
  "postalCode": "2560-364",
  "city": "TORRES VEDRAS",
  "country": "PT",
  "hours": ["MO 12:00-15:00", "MO 19:00-23:00"],
  "profileUrl": "https://www.pai.pt/paginas/428034-restaurante-sashimi"
}
```

### Key output fields

| Field | Notes |
|---|---|
| `listingId` | Numeric pai.pt id |
| `phone` / `phones` | From `tel:` and JSON-LD |
| `email` | Profile mailto, then optional website harvest |
| `website` | Independent site (`visit-webpage`), not pai.pt |
| `hours` | `MO 12:00-15:00` lines from `data-schedule` |
| `latitude` / `longitude` | Profile geo |

### FAQ

**Do I need a proxy?** Not on current HTML. Turn one on only if a run comes back empty or challenged.

**Does a city filter work?** Yes. The actor hits `/location_suggestions` and prefers the municipality `data-id`.

**Why is email missing?** Many profiles only publish a phone. Harvest the business website, or accept phone-only rows.

### Support

Questions and issues on the [actor page](https://apify.com/memo23/paginasamarelas-scraper).

### Disclaimer

Use this actor in line with Páginas Amarelas terms and applicable law. You are responsible for how you store and contact the people and companies in the dataset.

### SEO Keywords

paginas amarelas scraper, pai.pt scraper, portugal yellow pages, páginas amarelas leads, portuguese business emails, lisboa directory scraper

# Actor input Schema

## `startUrls` (type: `array`):

Paste pai.pt search or profile links. Examples: <code>https://www.pai.pt/searches?search\[query]=restaurante</code>, <code>https://www.pai.pt/searches?search\[query]=canalizador\&search\[location]=Lisboa</code>, or <code>https://www.pai.pt/paginas/428034-restaurante-sashimi</code>.

## `searchTerms` (type: `array`):

What you would type into Páginas Amarelas, e.g. <b>restaurante</b>, <b>canalizador</b>, <b>advogado</b>, <b>hotel</b>. One row per term. Every term is searched in every city below. Leave cities empty for a nationwide PT query. A pai.pt /searches or /paginas/ URL also works here.

## `locations` (type: `array`):

Portuguese city or region, e.g. <b>Lisboa</b>, <b>Porto</b>, <b>Braga</b>, <b>Faro</b>. Empty = nationwide. Resolved to <code>search\[location\_id]</code>.

## `sort` (type: `string`):

Same radios as pai.pt. <b>Relevance</b> is the site default.

## `openNow` (type: `boolean`):

Only listings pai.pt marks as <b>aberto agora</b>.

## `maxItems` (type: `integer`):

Stop after this many unique businesses across the whole run. Free plan is capped at 50.

## `scrapeDetails` (type: `boolean`):

Loads the /paginas/{id} page for email, website, hours, and coordinates. Turn off to keep search-card fields only.

## `harvestWebsiteEmail` (type: `boolean`):

If the directory profile has no inbox, fetch the business website homepage/contact page.

## `maxPages` (type: `integer`):

Page N is <code>/searches?search\[query]=…\&page=N</code>.

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

How many pages and profiles to load at the same time.

## `proxy` (type: `object`):

Leave off. Search and profile pages currently answer without Apify Proxy. Use RESIDENTIAL+Unblocker only if a run returns 403 / a challenge page.

## Actor input object example

```json
{
  "searchTerms": [
    "restaurante"
  ],
  "locations": [
    "Lisboa"
  ],
  "sort": "relevance",
  "openNow": false,
  "maxItems": 50,
  "scrapeDetails": true,
  "harvestWebsiteEmail": true,
  "maxPages": 20,
  "maxConcurrency": 5,
  "proxy": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (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 = {
    "searchTerms": [
        "restaurante"
    ],
    "locations": [
        "Lisboa"
    ],
    "proxy": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/paginasamarelas-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 = {
    "searchTerms": ["restaurante"],
    "locations": ["Lisboa"],
    "proxy": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("memo23/paginasamarelas-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 '{
  "searchTerms": [
    "restaurante"
  ],
  "locations": [
    "Lisboa"
  ],
  "proxy": {
    "useApifyProxy": false
  }
}' |
apify call memo23/paginasamarelas-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/paginasamarelas-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/7WAYPDwjLilRzevT0/builds/XrrPG31HWREqFcYdo/openapi.json