# 1182.ee Estonia Scraper (`memo23/1182-ee-scraper`) Actor

Scrape 1182.ee (Infotelefon) into one row per Estonian business: name, phone, email when listed, website, address, registry code. Keyword plus city, nationwide EE, or an /otsing/ or profile URL. JSON or CSV out. $5 per 1,000 listings plus phone and email events.

- **URL**: https://apify.com/memo23/1182-ee-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 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

## 1182.ee Estonia Scraper

Scrape [1182.ee](https://www.1182.ee/) (Infotelefon) into one row per **business**: name, phone, email when listed, website, address, registry code, coordinates.

Works from a keyword plus optional city, a nationwide term, or a pasted `/otsing/` or company-slug URL. Direct fetches time out; the actor defaults to Estonian residential 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, email, website, address, and registry code sit on the search card.
- Profile pages add map coordinates when 1182 embeds them.
- City is `{term}+{City}` in `/otsing/` — `?where=` / `?city=` on the live site do nothing.
- Optional harvest of the business site when the directory has no inbox.

### Overview

Built for lead lists and local research on Estonian companies. Each dataset item is one listing from 1182.ee.

### Supported inputs

| Input | What it does |
|---|---|
| `startUrls` | `https://www.1182.ee/otsing/restoran` or `/aladdin-restoran-tallinnas` |
| `searchTerms` | What you type in 1182, e.g. `restoran`, `hotell` |
| `locations` | City appended as `+City`. Empty = nationwide |
| `maxItems` | Stop after N unique listings (free plan cap 50) |
| `harvestWebsiteEmail` | Fetch the business site if the profile has no inbox |
| `proxy` | Default `RESIDENTIAL` + `EE` |

Unsupported: `?where=` / `?city=` query filters (the site ignores them). County slugs such as `/otsing/restoran/harjumaa` work.

### Use cases

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

### How it works

1. Build `https://www.1182.ee/otsing/{term}` or `/{term}+{City}`. Page N is `/{N}`.
2. Parse `.company-view-all` cards (`data-id` for the listing id).
3. Open `/{company-slug}` for map coordinates.
4. Charge `contact-phone` / `contact-email` after `pushData`.
5. If still no email and harvest is on, fetch the business homepage/kontakt page.

### Input configuration

| Field | Type | Required | Notes |
|---|---|---|---|
| `startUrls` | url\[] | one of terms/URLs | `/otsing/` or company slug |
| `searchTerms` | string\[] | one of terms/URLs | e.g. `restoran` |
| `locations` | string\[] | no | e.g. `Tallinn` |
| `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 EE residential |

#### Example input

```json
{
  "searchTerms": ["restoran"],
  "locations": ["Tallinn"],
  "maxItems": 10,
  "harvestWebsiteEmail": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "EE"
  }
}
```

### Output overview

One JSON object per business. Search cards already carry phone, email, website, address, and registry code. Profiles add latitude/longitude when the map embed is present. Opening hours are rarely published on public 1182 pages.

### Output samples

```json
{
  "listingId": "170319",
  "name": "Aladdin restoran Tallinnas",
  "phone": "+3726628330",
  "email": "info@aladdin.ee",
  "website": "http://www.aladdin.ee",
  "address": "Sõle 81, 10312 Tallinn, Harjumaa",
  "city": "Tallinn",
  "postalCode": "10312",
  "region": "Harjumaa",
  "country": "EE",
  "latitude": 59.45405,
  "longitude": 24.690159,
  "profileUrl": "https://www.1182.ee/aladdin-restoran-tallinnas",
  "source": "1182"
}
```

### Key output fields

| Field | Notes |
|---|---|
| `listingId` | Numeric 1182 `data-id` |
| `phone` / `email` / `website` | From the card or profile; directory `@1182.ee` inboxes are dropped |
| `registryCode` | Äriregister number when listed on the card |
| `latitude` / `longitude` | From the profile map embed |

### FAQ

**Does a city filter work?** Yes, as `{term}+{City}` in the path. Tallinn search IDs do not overlap the nationwide first page.

**Do I need a proxy?** Yes. 1182.ee times out from datacenter and from outside Estonia. Leave the default EE residential group on.

**Hours?** Public company pages we sampled do not publish a week table.

### Support

Questions or a broken selector: open an issue on the actor page.

### Disclaimer

Use this actor in line with 1182.ee terms and applicable law. You are responsible for how you use the data.

# Actor input Schema

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

Paste 1182.ee search or profile links. Examples: <code>https://www.1182.ee/otsing/restoran</code>, <code>https://www.1182.ee/otsing/restoran+tallinn</code>, or <code>https://www.1182.ee/aladdin-restoran-tallinnas</code>. <code>?where=</code> / <code>?city=</code> on the site do nothing — city lives in the path as <code>{term}+{city}</code>.

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

What you would type into 1182.ee, e.g. <b>restoran</b>, <b>hotell</b>, <b>arst</b>, <b>advokaat</b>. One row per term. Every term is searched in every city below. Leave cities empty for a nationwide EE query.

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

Estonian city, e.g. <b>Tallinn</b>, <b>Tartu</b>, <b>Pärnu</b>, <b>Narva</b>. Empty = nationwide. City is appended as <code>/otsing/{term}+{City}</code>. A third path segment that is a number is a page; a county slug such as <code>harjumaa</code> also works.

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

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

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

Loads the company page for map coordinates and any fields missing from the search card. Search cards already carry phone, email, and website when 1182 lists them. Turn off to keep 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>/otsing/{term}/{N}</code> or <code>/otsing/{term}+{City}/{N}</code>.

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

How many pages and profiles to load at the same time. Keep this modest — 1182.ee is fetched over Estonian residential proxy.

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

Leave on Estonian residential. Direct and datacenter requests time out; <code>RESIDENTIAL</code> + <code>country-EE</code> is what 1182.ee answers.

## Actor input object example

```json
{
  "searchTerms": [
    "restoran"
  ],
  "locations": [
    "Tallinn"
  ],
  "maxItems": 50,
  "scrapeDetails": true,
  "harvestWebsiteEmail": true,
  "maxPages": 20,
  "maxConcurrency": 5,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "EE"
  }
}
```

# 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": [
        "restoran"
    ],
    "locations": [
        "Tallinn"
    ],
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "EE"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/1182-ee-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": ["restoran"],
    "locations": ["Tallinn"],
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "EE",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("memo23/1182-ee-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": [
    "restoran"
  ],
  "locations": [
    "Tallinn"
  ],
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "EE"
  }
}' |
apify call memo23/1182-ee-scraper --silent --output-dataset

```

## MCP server setup

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