# Kick Email Scraper (`leads-scraper/kick-email-scraper`) Actor Kick Email Scraper SD - Kick Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Kick results by keyword, location and email domain - Kick email extractor. - **URL**: https://apify.com/leads-scraper/kick-email-scraper.md - **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community) - **Stats:** 3 total users, 2 monthly users, 95.7% 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 ### Kick Email Scraper The **Kick Email Scraper** collects publicly indexed contact emails for Kick streamers and channels and delivers them as a clean, structured dataset ready for JSON or CSV export. Kick grew fast around live streaming: Just Chatting hosts, IRL streamers, esports and FPS channels, slots and casino streamers, music and DJ broadcasts. A large share of them publish a business inquiry address in their channel about section or in a linked bio. The Kick Email Scraper finds those addresses at scale. It builds keyword-driven Google searches against `kick.com`, parses each result block structurally, and extracts every email that matches the domains you specify. This is contact discovery through public search results. The Kick Email Scraper does not log in to Kick, does not use a Kick API, and does not open the Kick website — there is no browser, no JavaScript rendering, no authentication and no cookies. #### Who needs a Kick streamer email finder Brand partnership teams, esports agencies, energy-drink and peripheral sponsors, affiliate managers, talent scouts and researchers who need Kick creator contacts in bulk. Manually opening channel pages works for ten streamers. The Kick Email Scraper is what you use when the shortlist is five hundred, and it turns that afternoon of tab-juggling into a single automated run. *** ### Key Features of the Kick Email Scraper Everything listed here is genuinely implemented in the Kick Email Scraper. | Feature | What it does | |---|---| | Google SERP data collection | Builds `site:kick.com` queries and fetches result pages through the Apify GOOGLE\_SERP proxy | | Query expansion | Base, quoted and `intitle:` variants plus one variant per modifier, to beat Google's per-query result ceiling | | Domain filtering | Only emails ending in your listed domains are kept (`@gmail.com`, `@yahoo.com` by default) | | Global deduplication | One row per unique email across every query, page and keyword in the run | | Email normalisation | Handles `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, zero-width characters and the full-width `＠` | | Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals | | Boundary-correct matching | `@gmail.com` never matches 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 control | An `asyncio` worker pool runs queries in parallel with a shared stop signal on `maxEmails` | | Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session per request | | Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty | | Resumable state | Progress persists in the key-value store and saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING` | | Structural parser | Locates the `

` title then the smallest surrounding block, rather than trusting Google's CSS class names | | Whole-page fallback | A markup change degrades the crawler to "emails without account details", never to "no emails" | | Streaming dataset writes | Each lead is pushed to the Apify dataset the instant it is found | *** ### How the Kick Email Scraper Works The Kick Email Scraper pipeline has six stages and no moving parts you need to configure. 1. **Read input.** Keywords, optional location, email domains, limits and concurrency. 2. **Build queries.** Each keyword pairs with each domain into a `site:kick.com` search, for example `site:kick.com fps streamer "@gmail.com" "Brazil"`. 3. **Expand queries.** With `expandQueries` on, quoted and `intitle:` phrasings run too, plus one variant per modifier. Base queries always go first. 4. **Fetch result pages.** Asynchronous `aiohttp` requests through the Apify GOOGLE\_SERP proxy, with pagination up to `maxPagesPerQuery`. 5. **Parse blocks.** The parser reads the result title, site label and snippet as metadata for each candidate lead. 6. **Extract, deduplicate, store.** A domain-filtered regex pulls addresses out of the block text; new ones stream into the dataset, duplicates are dropped. Because the Kick Email Scraper reads only Google's public index, every field it returns was already visible to anyone who searched for it. *** ### What Data Does the Kick Email Scraper Extract Every item has the same 14 fields, so the output schema of the Kick Email Scraper is stable across runs and easy to map once into a CRM. | Field | Meaning | |---|---| | `network` | Platform name | | `keyword` | The keyword that produced the lead | | `query` | The exact Google query used | | `title` | Raw result title | | `accountName` | Account label Google prints | | `fullName` | Display name parsed from a profile-style title; empty for clip or VOD captions | | `username` | URL-safe Kick handle when one is exposed; otherwise `null` | | `profileUrl` | Canonical channel URL when a handle is known; otherwise empty | | `url` | Direct Kick link when exposed, else the profile URL | | `description` | Bio or caption snippet, cleaned of labels and engagement 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 | *** ### Input Fields Nine fields drive the Kick Email Scraper. Only `keywords` is required. | Field | Type | Default | Description | |---|---|---|---| | `keywords` | array (required) | `["streamer", "creator"]` | Search terms: niche, job title, industry | | `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 × domain pair in several phrasings | | `queryModifiers` | array | `["business inquiries", "email", "contact", "sponsorship"]` | Extra words combined with each keyword when expansion is on | | `maxPagesPerQuery` | integer 1–50 | `30` | Pagination cap per query | | `maxConcurrency` | integer 1–20 | `5` | Parallel queries | #### JSON input example ```json { "keywords": ["fps streamer", "just chatting", "esports creator"], "location": "Brazil", "customDomains": ["@gmail.com", "@outlook.com"], "maxEmails": 250, "countryCode": "BR", "expandQueries": true, "queryModifiers": ["business inquiries", "email", "contact", "sponsorship"], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` *** ### Output Schema and Dataset Export The Kick Email Scraper writes leads to the Apify dataset as they are discovered, so you can watch results accumulate mid-run. #### JSON output example ```json { "network": "Kick", "keyword": "fps streamer", "query": "site:kick.com fps streamer \"@gmail.com\" \"Brazil\"", "title": "AimlockLuna (@aimlockluna) - Kick", "accountName": "aimlockluna", "fullName": "AimlockLuna", "username": "aimlockluna", "profileUrl": "https://kick.com/aimlockluna", "url": "https://kick.com/aimlockluna", "description": "Daily FPS and ranked grind streams. Sponsorship and business inquiries: aimlockluna.biz@gmail.com", "email": "aimlockluna.biz@gmail.com", "emailDomain": "@gmail.com", "possiblyTruncated": false, "foundAt": "2026-08-31T11:07:44.201Z" } ``` Export the Kick Email Scraper dataset as JSON, CSV, XLSX or XML from the Apify console, or read it over the API into your own automation. *** ### How to Run It 1. Open the Kick Email Scraper on Apify and click **Try for free**. 2. Replace the default keywords with real Kick niches — `slots streamer`, `IRL streamer`, `valorant channel`, `music stream`. 3. Set the email domains you want. A narrow domain list produces a cleaner dataset than a broad one. 4. Optionally add a `location` and a `countryCode` — Kick's audience is heavily regional, so this matters more here than on most platforms. 5. Choose `maxEmails` and start the run. 6. Follow the live log: it reports pages fetched, blocked pages, retries and emails per page. 7. Export the dataset, or chain the Kick Email Scraper into a larger workflow via the Apify API. #### Tips for a better yield Give the Kick Email Scraper two or three specific keywords rather than one generic word. `creator` is vague; `valorant streamer` is a query that converts. Leave query expansion on. It is the single biggest lever on how many Kick streamer emails a run returns. When a niche dries up, change `customDomains` before you change the keyword. The same channels often list addresses on different providers. *** ### Use Cases for the Kick Email Scraper Teams reach for the Kick Email Scraper whenever a task begins with "find every Kick channel that…". | Use case | How the Kick Email Scraper helps | |---|---| | Sponsorship outreach | Build a target list of Kick streamers in a game or category and pitch them directly | | Affiliate and creator recruitment | Find streamers already reviewing peripherals, energy drinks or software | | Esports talent scouting | Source competitive players and coaches with a working contact route | | Influencer marketing campaigns | Assemble a shortlist with handles, bios and emails in one dataset | | Agency prospecting | Sell clipping, editing, thumbnail or channel-growth services to active streamers | | Market research | Map who streams in a Kick category and how they position themselves | | CRM enrichment | Append profile URLs and bio snippets to contacts you already hold | | Podcast and event booking | Recruit guests from a specific streaming niche | *** ### Why Choose This Actor Kick has no public creator directory with contact details, and its discovery surface changes constantly. The search-based extraction approach behind the Kick Email Scraper sidesteps that entirely. The Kick Email Scraper automates the tedious half of Kick lead generation — searching, paginating, copying, deduplicating — and leaves you the judgement calls. Because the Kick Email Scraper parses structurally instead of by CSS class name, and because a whole-page fallback exists, a Google layout change degrades quality rather than breaking your run. It also pairs naturally with its siblings. Streamers are multi-platform: run the [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) for the same names on Twitch, the [YouTube Email Scraper](https://apify.com/leads-scraper/youtube-email-scraper) for their VOD channels, and the [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) for creators who cross-post there. For the social layer around a stream, the [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) and [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) cover the two places Kick communities actually live, and the [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) catches the clip accounts that grow them. *** ### Limitations These constraints on the Kick Email Scraper are real. Read them before your first run. - **Only publicly indexed emails.** The Kick Email Scraper finds addresses Google has already crawled. A streamer who never published an email will not appear. - **Google's result cap.** One query returns roughly 300 results at most. That is exactly why query expansion exists — leave it enabled. - **`possiblyTruncated`.** When Google's snippet ellipsis touches an address, the row is flagged `true`. Verify those before you send anything. - **Apify GOOGLE\_SERP proxy required.** The Kick Email Scraper cannot run without Apify proxy credentials. - **Free-plan cap.** Free Apify plans are limited to 100 emails per run; paid plans are uncapped. - **`username` and `profileUrl` availability.** These fields are populated only when Kick exposes a handle in Google's result. Where Google prints only a display name, the row keeps `accountName` and `fullName` but has an empty `username` and `profileUrl`. That is a Google limitation, not a bug. - **Variable yield.** Output depends on keywords, domains and location. No volume is guaranteed. *** ### Example: a full run A typical Kick Email Scraper run with three keywords, two domains, expansion on and `maxEmails: 250`. The Kick Email Scraper sends base queries first (`site:kick.com esports creator "@gmail.com"`), then quoted and `intitle:` variants, then one variant per modifier — `business inquiries`, `email`, `contact`, `sponsorship`. Five queries run concurrently, each paginating until it runs dry or reaches `maxPagesPerQuery`. Addresses are normalised, domain-filtered, deduplicated globally and streamed to the dataset until the 250th unique email stops every worker. Blocked or failed queries are re-queued once at the end, so a transient CAPTCHA does not quietly cost you a whole keyword. *** ### Related Actors The Kick Email Scraper belongs to a family of contact-discovery Actors sharing this engine and output schema. | Actor | What it collects | |---|---| | [Kick Email and Phone Number Scraper](https://apify.com/leads-scraper/kick-email-and-phone-number-scraper) | Emails and phone numbers from Kick | | [Kick Phone Number Scraper](https://apify.com/leads-scraper/kick-phone-number-scraper) | Public phone numbers from Kick | | [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 | | [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 | | [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder | | [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 #### What is the Kick Email Scraper? An Apify Actor that extracts publicly indexed contact emails for Kick streamers and channels from Google search results and stores them as structured data. #### Does the Kick Email Scraper log in to Kick? No. The Kick Email Scraper does not log in, does not call a Kick API, and does not open kick.com. It reads Google search results only. #### Where do the emails actually come from? Titles, snippets and site labels in Google's public index — typically a business inquiry address a streamer wrote in their channel description. The Kick Email Scraper reads nothing else. #### Does the output schema ever change? No. Every item the Kick Email Scraper writes carries the same 14 fields, which keeps downstream mapping stable. #### Can I choose which email providers are returned? Yes. `customDomains` filters the Kick Email Scraper's extraction step. Defaults are `@gmail.com` and `@yahoo.com`, and the leading `@` is optional. #### Why is `username` empty on some rows? Google sometimes prints only a display name. When no handle is exposed, `username` is `null` and `profileUrl` is empty, while `accountName` and `fullName` remain populated. #### What does `possiblyTruncated: true` mean? Google's snippet ellipsis touched the address, so it may be cut off. Treat those rows as unverified. #### How many Kick streamer emails will one run return? It depends on keywords, domains and location — no volume is guaranteed. Free Apify plans stop at 100 emails per run; paid plans are uncapped. #### Do I need a proxy? Yes. The Kick Email Scraper requires the Apify GOOGLE\_SERP proxy and will not run without Apify proxy credentials. #### Should I leave query expansion on? Almost always. Google caps a single query near 300 results, and expansion is how the Kick Email Scraper works around that ceiling. #### Is this affiliated with Kick? No. It is an independent Apify Actor, not endorsed by or connected to Kick. #### What happens if a run is interrupted? Resumable state lives in the key-value store and saves on `PERSIST_STATE`, `MIGRATING` and `ABORTING`, so a migrated run resumes instead of restarting. #### Can I export to CSV or schedule recurring runs? Yes. Export as JSON, CSV, XLSX or XML, and use Apify Schedules to run the Kick Email Scraper nightly or weekly into the same dataset. *** ### Leave a review If the Kick 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 instead - bugs get fixed faster than they get complained about. ### Support Questions about the Kick Email Scraper, feature requests, or need a custom build? Email **neurodata.apify@gmail.com**. Not affiliated with, endorsed by, or officially connected to Kick. Use collected data in line with applicable privacy and anti-spam law. # Actor input Schema ## `keywords` (type: `array`): Search terms describing the Kick 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 Kick. ## `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": [ "streamer", "creator" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "maxEmails": 20, "countryCode": "", "expandQueries": true, "queryModifiers": [ "business inquiries", "email", "contact", "sponsorship" ], "maxPagesPerQuery": 30, "maxConcurrency": 5 } ``` # Actor output Schema ## `results` (type: `string`): Records produced by Kick 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "streamer", "creator" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "business inquiries", "email", "contact", "sponsorship" ] }; // Run the Actor and wait for it to finish const run = await client.actor("leads-scraper/kick-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [ "streamer", "creator", ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com", ], "countryCode": "", "queryModifiers": [ "business inquiries", "email", "contact", "sponsorship", ], } # Run the Actor and wait for it to finish run = client.actor("leads-scraper/kick-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": [ "streamer", "creator" ], "location": "", "customDomains": [ "@gmail.com", "@yahoo.com" ], "countryCode": "", "queryModifiers": [ "business inquiries", "email", "contact", "sponsorship" ] }' | apify call leads-scraper/kick-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/kick-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 ` 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/crPKudxsCXgqVbFBe/builds/LKqgvBPt66fp9547S/openapi.json