# Changelog of Facebook Events Scraper · No Login · $2/1k (`alfalfa/facebook-events-scraper`) Actor

- **URL**: https://apify.com/alfalfa/facebook-events-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/alfalfa/facebook-events-scraper.md

## Changelog

### 2026-09-23 (proxy)

- Runs that use Apify Proxy now always go through the residential proxy group, even when the input selects no group or a different one. Before, an empty group list meant datacenter proxies, which Facebook answers with a login wall or a rate-limit error, so such runs returned nothing. The run log says so in one line.
- No extra cost: you pay per event, and proxy usage is not billed to you.

### 2026-09-17 (prices)

- Prices lowered: $3 per 1,000 events on the free plan, $2.70 / $2.40 / $2 on Starter / Scale / Business (was $5 / $4.50 / $4 / $3.50). The organizer email lookup stays at $0.01 per event that returned one. No start fee; the price per event is the final price, platform usage included.

### 2026-09-15 (run log)

- Network error messages in the run log no longer include server addresses.

### 2026-09-09

- Facebook rate-limit answers on the listing wait longer before the retry, and every request now gets seven attempts, so a rough proxy minute no longer loses an event or a search.
- Store description and README now name the plain use cases (Facebook events scraper, events API replacement, n8n, Make, Zapier, AI agents via MCP).
- A page that Facebook does not show without a login (private profile, restricted page, wrong URL) no longer ends the run as failed: the run finishes with a status message saying which URLs could not be scraped, and nothing is charged for them.
- Search pages that come back without results are fetched again before being given up on, so a one-off bad response does not lose the search.
- Organizer email lookups are retried once when interrupted.
- The scraper always uses a residential proxy on the platform, even when the proxy is switched off in the input (Facebook blocks direct requests, so such runs could only fail).
- Small platform hiccups (input download, billing calls) are retried instead of failing the run.
- Example input lowered to 50 events so the Store example finishes quickly.

### 2026-09-08

- Proxy handling hardened: the scraper checks its route at start and switches to a backup route by itself if the primary one fails, so runs finish instead of erroring.
- The proxy country picked in the input now applies to the default residential route as well.

### 2026-09-07

- Run budget is honoured: set a maximum cost per run and the scraper stops before it is exceeded, instead of leaving the traffic running once the platform stops charging.
- `usersGoing` and `usersInterested` are filled for events opened directly by URL where Facebook search can still find the event by name.
- README rewritten with a worked pricing example, an explicit list of what is never charged, and a guide to exporting into Google Calendar.
- Five ready-made example runs published, including city search, page programmes and organizer emails.

### 2026-09-07 (first release)

- Search public events by keyword, city, page URL, explore URL or a single event URL.
- Every date of a recurring event returned in `childEvents`, not just the next one.
- Optional organizer email, charged only when an address is actually found.
- Output field names match the official Facebook Events Scraper.