Facebook · Events
Facebook Events Search Scraper API
- 0.15¢ per call
- $1.49 per 1,000
- Takes a search query
- Errors and timeouts are not charged
On Facebook
Events
The call
One GET, and the events search comes back as JSON.
Your key goes in one header. 1 required parameter, and the answer is the object below it.
The full referencecurl "https://hproxy.com/api/v1/scrape/facebook/events-search?query=coffee" \
-H "X-API-Key: hpx_your_key_here"{
"events": [
{ "id": "88120...", "title": "Launch night", "startTime": "2026-08-14T18:00:00Z",
"venue": { "name": "The Hall", "city": "Berlin" },
"attendance": { "going": 412, "interested": 1890 } }
]
}What comes back
The Facebook events search object.
- events[]
- Each event with title, description and cover image.
- startTime / endTime
- Scheduled start and end, with timezone.
- venue
- Location name, address and coordinates where public.
- attendance
- Going and interested counts.
What it takes
Parameters.
Search term or keyword.
Pagination token from the previous response.
How it works
Scraping Facebook events search, in three steps.
You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.
- 1
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product. - 2
Grab your API key
One key from the dashboard authenticates every scraper. - 3
Call the endpoint
Send the GET you need and read the JSON. That is the entire integration.
What people build with it
Where the Facebook events search endpoint earns its keep.
- Aggregate what is happening in a city into your own listings.
- Track competitor and community events automatically.
- Alert on new events matching a topic or venue.
Facebook events search questions
Answered before you ask.
Send one authenticated HTTPS request to the Facebook Events Search endpoint with a search query and your HProxy API key. Search Facebook events by keyword and get ranked results back with title, venue, start time and attendance counts. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.
This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.
No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.
A structured JSON object with the full events search data Facebook exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.
Yes. The response carries a cursor; pass it back on the next call to continue from where you stopped. Each page is one billable call, so you only pay for the depth you actually pull.
The API only accesses publicly available Facebook data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and Facebook's terms for your use case.
Docs and AI
Connect your scraper to an AI, any time.
The whole Scraper API is published as markdown, so an assistant reads every endpoint, every parameter and a real response without a key and writes your integration. And because a scrape is one GET that answers in JSON, an agent can run the scraper itself, on its own schedule, with your key.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
The API as markdown
Paste /llms/scraper-api.txt into Claude, ChatGPT, Cursor or Copilot: every endpoint and the whole catalog, in one file. No key and no account to read it.
An agent can call it
One GET with your key returns structured JSON, so an agent scrapes on its own schedule. No browser to drive, no parser to keep alive between runs.
MCP server and CLI
Built by us for the free tools and hosted at mcp.hproxy.com: the proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor or any assistant that speaks MCP. Nothing to install, no key.
API docs
Every scraper endpoint documented end to end, with the parameters it takes and the response it really returns.
Events elsewhere
The same data on 1 other platform.
One key, one JSON shape, one balance. Move sideways without learning a second API.
More from Facebook
17 Facebook endpoints, one key.
Every platform
The same key works on all 23.
- TikTok Scraper API23 endpoints · $1.49/1k
- Facebook Scraper API17 endpoints · $1.49/1k
- YouTube Scraper API13 endpoints · $1.49/1k
- Instagram Scraper API11 endpoints · $1.49/1k
- LinkedIn Scraper API6 endpoints · $1.49/1k
- Twitter / X Scraper API6 endpoints · $1.49/1k
- Reddit Scraper API5 endpoints · $1.49/1k
- Threads Scraper API5 endpoints · $1.49/1k
- Google Scraper API4 endpoints · $1.49/1k
- Pinterest Scraper API4 endpoints · $1.49/1k
- Twitch Scraper API4 endpoints · $1.49/1k
- Bluesky Scraper API3 endpoints · $1.49/1k
- Truth Social Scraper API3 endpoints · $1.49/1k
- Spotify Scraper API3 endpoints · $1.49/1k
- Snapchat Scraper API1 endpoint · $1.49/1k
- SoundCloud Scraper API1 endpoint · $1.49/1k
- Kick Scraper API1 endpoint · $1.49/1k
- Linktree Scraper API1 endpoint · $1.49/1k
- Komi Scraper API1 endpoint · $1.49/1k
- Pillar Scraper API1 endpoint · $1.49/1k
- Linkbio Scraper API1 endpoint · $1.49/1k
- Linkme Scraper API1 endpoint · $1.49/1k
- Amazon Scraper API1 endpoint · $1.49/1k
More on the Facebook Events Search API
What the Facebook Events Search endpoint returns
Search Facebook events by keyword and get ranked results back with title, venue, start time and attendance counts. The JSON object carries events[], startTime / endTime, venue and attendance. Nothing is summarised away on our side, so what you read in the response is what the Facebook events search page itself holds.
What you send to the Facebook Events Search API
The call takes a search query. Required: query. Optional: cursor. Your key travels in the X-API-Key header, the response is JSON, and the call is billed at 0.15¢, $1.49 per 1,000.
Events on other platforms
The same events data is available on 1 other platform: Twitch User Schedule. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from Facebook to another network is a change of URL rather than a second integration.
Is scraping Facebook events search allowed?
The endpoint reads publicly available Facebook data, the same pages anyone can open in a browser without logging in. It does not touch private accounts or anything behind a password. How you then use the data is yours to keep lawful, under the rules that apply to you and to Facebook.
Ready when you are.
Your dashboard is ten seconds away. No sales call, no subscription, no minimum.