# Sikayetvar Turkey Consumer Complaint Registry Scraper (`jungle_synthesizer/sikayetvar-turkey-consumer-complaint-registry-scraper`) Actor

Scrapes Turkey's national consumer-complaint registry (Şikayetvar) — brand accountability metrics, full complaint text, and the reviewer cross-brand graph.

- **URL**: https://apify.com/jungle\_synthesizer/sikayetvar-turkey-consumer-complaint-registry-scraper.md
- **Developed by:** [BowTiedRaccoon](https://apify.com/jungle_synthesizer) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 record scrapeds

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

## Sikayetvar Turkey Consumer Complaint Registry Scraper

Scrape [Şikayetvar](https://www.sikayetvar.com) — Turkey's national consumer-complaint registry — for full complaint text, brand accountability metrics (response rate, complaint volume), and the reviewer cross-brand graph. Walk the entire A–Z brand index, target specific brands, or trace a specific reviewer's complaint history across every brand they've filed against.

### What it does

Şikayetvar is the surface every Turkish consumer lands on when searching `<brand> şikayet` — a public register of consumer complaints against ~200k+ Turkish and international brands. This actor covers three angles most complaint-registry scrapers skip:

- **Full complaint text** — the complete complaint body, not a truncated excerpt, plus category tag, view count, and the reviewer who filed it.
- **Brand accountability** — response rate (% of complaints answered in the last year), aggregate rating, total review count, and sub-brand/product slugs, saved alongside the brand's complaints.
- **The reviewer graph** — every reviewer profile enumerates the full set of brands that reviewer has complained about, making cross-brand pattern detection possible (repeat complainers, coordinated activity, etc.).
- **Complaint velocity** — 30-day vs. trailing-90-day complaint counts, sampled from what's crawled in the run, so you can spot a brand's complaint volume trending up or down.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `mode` | Select | `complaints` (default) — full complaint text + brand row. `brands` — brand census only, no pagination. `reviewers` — reviewer profiles + cross-brand edge list. |
| `brandSlugs` | Array | Specific brand slugs to crawl (e.g. `turkcell`, `turk-telekom` — the last path segment of the brand's Şikayetvar URL). Leave empty to walk the full A–Z brand index. |
| `reviewerHandles` | Array | Specific `/uye/` reviewer handles to crawl (e.g. `nureliz-17451364`). Leave empty to discover handles from the site-wide newest-complaint feed. Used by `reviewers` mode. |
| `maxPagesPerBrand` | Integer | Complaint-listing pages to walk per brand (24 complaints/page; some brands run to 200+ pages). Default 10. |
| `fetchComplaintDetails` | Boolean | When enabled, also fetches each complaint's own page for `complaint_status`, the company's reply text/date, and `comment_count`. Off by default (roughly doubles request volume). |
| `maxItems` | Integer | Maximum number of records to save. |

### Output

Three record shapes, distinguished by `record_type`.

**Brand row** — one per brand crawled, saved before its complaints:

```json
{
  "record_type": "brand",
  "brand_slug": "turkcell",
  "brand_name": "Turkcell",
  "brand_url": "https://www.sikayetvar.com/turkcell",
  "brand_telephone": "+902123131000",
  "brand_address_locality": "Maltepe",
  "brand_address_region": "İstanbul",
  "aggregate_rating": 32,
  "aggregate_review_count": 13095,
  "response_rate_pct": 87,
  "subbrand_slugs": "turkcell/faturali-paketler|turkcell/esim",
  "complaints_last_30d": 9,
  "complaints_last_90d": 24,
  "complaint_velocity_delta_pct": 12.5
}
```

**Complaint row** — one per complaint, with the full body text:

```json
{
  "record_type": "complaint",
  "complaint_id": "turkcell/otomatik-odeme-hatasi-427-tl-fazla-cekildi",
  "complaint_url": "https://www.sikayetvar.com/turkcell/otomatik-odeme-hatasi-427-tl-fazla-cekildi",
  "complaint_headline": "Otomatik Ödeme Hatası 427 TL Fazla Çekildi, İade Bekleniyor",
  "complaint_body": "Turkcell hattımda kullandığım Rahat paketim için otomatik ödeme talimatım bulunuyor...",
  "date_published": "2026-08-21",
  "product_or_service": "rahat-paketler",
  "complaint_category": "Rahat Paketler",
  "reviewer_handle": "muhammed-14121033",
  "reviewer_display_name": "Muhammed",
  "brand_slug": "turkcell"
}
```

**Reviewer row** — one per reviewer profile, with the cross-brand edge list:

```json
{
  "record_type": "reviewer",
  "reviewer_handle": "nureliz-17451364",
  "reviewer_display_name": "Nureliz",
  "reviewer_complaint_count": 4,
  "reviewer_brands_complained_about": "turk-telekom|turkcell"
}
```

`complaint_status`, `company_responded`, `company_response_text`, `company_response_date`, and `comment_count` are only populated when `fetchComplaintDetails` is enabled.

### Use cases

- **Brand reputation monitoring** — track a competitor's or your own complaint volume, response rate, and unresolved complaint text.
- **ORM agencies** — surface every open complaint a client hasn't responded to yet, ranked by view count.
- **Review-fraud / astroturf detection** — the reviewer graph exposes accounts complaining across an unusual number of unrelated brands.
- **Sales prospecting** — find a competitor's angriest customers and the specific issues driving churn.
- **Market research** — census the brand index for complaint density by category.

### Technical notes

- Full complaint text is captured on the listing page — no per-complaint detail fetch needed unless you opt into `fetchComplaintDetails`.
- Discovery walks the site's own A–Z brand index; there is no sitemap to rely on.
- The run's `resumeCursor` (in the output) carries the crawl position forward — pass it back in on your next run to continue a large A–Z walk instead of restarting from the top.
- Reaches Turkish content reliably, wherever you run it.

# Actor input Schema

## `sp_intended_usage` (type: `string`):

What will this data feed? E.g. lead lists, KYB checks, price tracking.

## `sp_improvement_suggestions` (type: `string`):

Provide any feedback or suggestions for improvements.

## `sp_contact` (type: `string`):

We'll personally help with your use case. No spam.

## `resumeCursor` (type: `string`):

Leave empty for a fresh crawl. To CONTINUE a previous run where it stopped — without paying again for records you already received — paste the `resumeCursor` value from that run's Output (the run's OUTPUT key). Resume promptly: the previous run's data expires with your account's retention window (free tier: your ~10 most recent runs).

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

'complaints' walks a brand's complaint stream (full body + a brand-accountability summary row). 'brands' is a cheap brand-only census (page 1, no complaint pagination). 'reviewers' walks reviewer profiles for the cross-brand edge list.

## `brandSlugs` (type: `array`):

Specific brand slugs to crawl directly (e.g. "turkcell", "turk-telekom" — the last path segment of the brand's Şikayetvar URL). Leave empty to walk the full A-Z brand index. Used by 'complaints' and 'brands' modes.

## `reviewerHandles` (type: `array`):

Specific /uye/ reviewer handles to crawl directly (e.g. "nureliz-17451364"). Leave empty to discover handles from the site-wide newest-complaint firehose. Used by 'reviewers' mode.

## `maxPagesPerBrand` (type: `integer`):

Complaint-listing pages to walk per brand (24 complaints/page; some brands run to 200+ pages). Also bounds firehose pages walked in 'reviewers' mode without explicit handles.

## `fetchComplaintDetails` (type: `boolean`):

When enabled, fetches each complaint's own page for complaint\_status, the company's reply text/date, and comment\_count. Roughly doubles request volume — off by default.

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

Maximum number of records to save.

## Actor input object example

```json
{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "mode": "complaints",
  "brandSlugs": [],
  "reviewerHandles": [],
  "maxPagesPerBrand": 3,
  "fetchComplaintDetails": false,
  "maxItems": 10
}
```

# Actor output Schema

## `results` (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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "mode": "complaints",
    "brandSlugs": [],
    "reviewerHandles": [],
    "maxPagesPerBrand": 3,
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jungle_synthesizer/sikayetvar-turkey-consumer-complaint-registry-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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "mode": "complaints",
    "brandSlugs": [],
    "reviewerHandles": [],
    "maxPagesPerBrand": 3,
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jungle_synthesizer/sikayetvar-turkey-consumer-complaint-registry-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 '{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "mode": "complaints",
  "brandSlugs": [],
  "reviewerHandles": [],
  "maxPagesPerBrand": 3,
  "maxItems": 10
}' |
apify call jungle_synthesizer/sikayetvar-turkey-consumer-complaint-registry-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jungle_synthesizer/sikayetvar-turkey-consumer-complaint-registry-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/IsUW4ZS5LoHqBC3zA/builds/BDdcerVvLbM05I7Ls/openapi.json