Facebook hub

Facebook Events Search API

Keyword search over public Facebook events — structured rows in the same envelope as the rest of the Facebook tag.

GET /v1/facebook/events/search

1 credit per successful request.

About this endpoint

`GET /v1/facebook/events/search` takes a required `query` and returns matching events under `data.events`. When `data.page.hasMore` is true, pass `data.page.nextCursor` as `cursor` on the next call. Bill from `meta.creditsCharged`; the flat amount for this operation is on this page and in the OpenAPI note.

This is name search, not city explore and not a single-event detail lookup. All Facebook routes share one Social Fetch API key.

Facebook Events Search API FAQ

What does the Facebook Events Search API return?

A page of events under data.events, the echoed query under data.query, totalEvents for this page, and pagination under data.page (hasMore, nextCursor). Each event can include id, url, name, startAt, place, cover, and attendance counts. Responses use the shared Social Fetch envelope with meta.requestId and meta.creditsCharged.

How do I search Facebook events by name via API?

Send GET /v1/facebook/events/search with x-api-key and a required query parameter. Optionally add cursor from a previous page. Full examples are in the API docs.

How much does Facebook event search cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Each paginated page is a separate billed request.

How does pagination work on Facebook events search?

When data.page.hasMore is true, pass data.page.nextCursor as the cursor query param on the next request. Keep the same query across pages.

Do I need a Facebook account or Graph API token to search events?

No. You authenticate to Social Fetch with an API key. The route reads public Facebook events search results; it does not act on behalf of a Facebook account you manage.