OLX.pl Scraping Specialist Needed (Phone Numbers)
Hello,
We are looking for an experienced web scraping specialist to scrape phone numbers from olx.pl listings.
We already have a database of listings. Your task will be to:
fetch listings from our API,
scrape phone numbers from OLX offers,
send the scraped phone numbers back to our system via our API endpoint.
Scope of work:
Scrape 4,000 phone numbers per day
Continuous operation for 4 consecutive days
Minimum total result: 4,000 phone numbers within any 24-hour period
The project will be considered completed after 4 days of successful testing
Technical requirements:
Ability to bypass bot detection (403, anti-bot mechanisms, etc.)
Stable, uninterrupted scraper execution for 4 days
Scraper must run on our VPS:
Linux (headless) or
Windows (headful via RDP)
Retry mechanism for listings without visible phone numbers:
Up to 3 retry attempts
If still unavailable, mark as NOPHONE
Proper logging and error handling
We provide:
Residential IP address
Up to 20 OLX accounts (sessions can be created if required)
API access for input (offers) and output (phone numbers)
Success criteria:
Achieving at least 4,000 valid phone numbers within 24 hours
Stable performance during the 4-day test period
Please apply only if you have proven experience with large-scale scraping, bot protection bypassing, and long-running scrapers.
-
Winning proposal8 days404 USD
1017 2 1 Winning proposal8 days404 USDHi Krzysztof,
I’m applying to officially take on the OLX.pl scraper project. Based on our previous discussion and the technical requirements, here is my proposal:
Implementation Plan:
Phase 1 (Prototype): I will start by configuring 2-3 accounts with an Amazon captcha solver (AWS WAF Task) to bypass the initial challenges. I’ll process the first 500 numbers to verify stability.
Phase 2 (Scaling): After the prototype succeeds, I’ll scale to all 10-20 accounts and implement the full 96-hour continuous run to reach the target of 4,000 numbers/day.
…
Architecture: The scraper will use Session Persistence to minimize CAPTCHA costs and protect your proxy reputation.
Terms:
Budget: 1,800 PLN. This covers the high complexity of the AWS WAF bypass, multi-account session management, and the required 4-day monitoring period.
Timeline: 8 days (includes development, account setup, and the mandatory 4-day stability test).
-
Для успішної реалізації цього проекту, у вас мають бути вже відтестовані "ліміти" олх по акаунтах.. І саме головне, ці акаунти мають бути вже "прогріті". Ну а далі справа за проксі, найкраще мобільні.. і тільки після цього, вже код програміста. Тобто для успішного тесту 4000 номерів, тут треба спочатку від вас якісні дані . У вас є такі?
-
yes sir
-
Який бюджет по виконанню задачі?
Це задача не стільки на парсинг, скільки на обхід захисту (Anti-Bot Bypass), тому цікавить який ваш бюджет на цю задачу. -
Warszawa