# Facebook Events API (https://www.socialcrawl.dev/platforms/facebook/events)

> Returns the events listed under a Facebook city or region Events explore page. **The `url` must be an Events explore URL ending in the numeric location id** (see the example); a plain page URL is rejected with a 400 at 0 credits, and a single page's OWN events are `/v1/facebook/profile/events`. Each row carries the title, the permalink, the cover image, the start time, the RSVP counts, and on `post.ext.event` the rendered time line (`time_text`), `location_name` (the venue), `start_timestamp`, `is_online`, `is_past`, `interested_count` and `going_count`. The same two reading notes apply as on that endpoint: `published_at` is the event's START time and is routinely in the future, and `engagement.views` and `engagement.likes` carry the interested and going RSVP counts because an event has no views or likes. The explore listing carries no description, address, city, host or category, so those are null on a plain call. Send `include=details` and every event is joined, in the same call, to the per-event details lookup: the description, the street address and city, the coordinates, the hosts (`hosts[]`, and the one-line host credit on `post.author.display_name` and `post.ext.event.host_context_text`), the category, the privacy, the cancelled flag and the attendance count land on each row, and a missing cover or RSVP count is filled where the details carry one. Values the row already carried are never replaced. Cost: 1 credit for the page plus 1 credit per event filled from a fresh lookup (at most 12 events a page, so 13 credits at most); rows already in cache are filled for free, rows that could not be filled are refunded, and a repeat of the same call within the cache window is 0 credits. Time: `include=details` adds 2 to 8 seconds on a fresh page (the lookups run in parallel and the call waits for the slowest, never more than 12 seconds) and nothing when the rows are already cached. The response carries a `hydration` block itemising rows, lookups, cache hits, credits and milliseconds. Filter by relative `time` (defaults to all time) and forward the returned cursor for additional pages.

TL;DR: `GET /v1/facebook/events` costs 1 credit for the page. include=details holds 1 credit per event (at most 12 a page) and keeps only the rows filled from a fresh lookup, so a page is at most 13 credits; rows served from cache are free, unfilled rows are refunded, and a repeat of the same call within the cache window costs 0. With `max_pages`, `max_items` or `max_credits`, each page walked is billed at this price (a cached page is free), and `max_credits` caps the total. and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | yes | Full URL of the city's Facebook Events page. |
| `time` | no | Relative time window. Defaults to all time when omitted. (today \| this_week \| next_week) |
| `cursor` | no | Cursor returned by the previous response for pagination. |
| `include` | no | Set to `details` (one token only) to fill, on every event in this one call, `post.ext.event.description`, `address`, `city`, `latitude`, `longitude`, `hosts`, `host_context_text`, `category`, `privacy`, `is_canceled` and `attendance_count`, and the host credit on `post.author.display_name`. Holds 1 credit per event (at most 12 a page) and keeps only the rows filled from a fresh lookup; rows already in cache and rows the lookup cannot fill are refunded, so a page is never more than 13 credits. The join takes 2 to 8 seconds on a fresh page, never more than 12, and nothing when the rows are already cached; read `data.hydration` for the rows, the credits held and kept, and the time. Without it the call is unchanged. (details) |
| `since` | no | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| `until` | no | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. |
| `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. |
| `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/facebook/events" \
  --data-urlencode "url=https://www.facebook.com/events/explore/saint-petersburg-florida/111326725552547" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What is the Facebook Events API?

GET /v1/facebook/events lists Facebook events for a city. Pass the city events page url and the response returns each event with its name, date, venue, and cover image. It costs 1 credit per call.

### What URL do I pass?

Pass the Facebook city events page URL in the url param, for example the /events/ page for a given city. The endpoint reads that page and returns the structured event list, so you do not have to parse the HTML yourself.

### How do I page through more events?

Take the cursor value from the response and pass it as the cursor param on the next call to load the next page of events. Repeat until the cursor comes back empty.

### Can I filter by date or time?

Yes. Use the optional time param to narrow the events window. Combine it with cursor pagination to build a rolling feed of upcoming local events for an event discovery pipeline.

### How is this better than the Graph API?

It returns city event listings as clean JSON behind one x-api-key, without app review, tokens, or Graph API scopes. Each call is 1 credit, and new accounts get 100 free credits with no card.

### Can I get each event's description and address too?

Add include=details. The explore listing carries the title, the cover image, the start, the venue, and the RSVP counts; the join fills the description, the street address and city, the coordinates, the hosts, the category, the privacy, and the cancelled flag on every row in the same call. The page is 1 credit plus 1 credit per event filled from a fresh lookup, 13 credits at most, with cached rows free and unfilled rows refunded.

See the full Facebook API: https://www.socialcrawl.dev/platforms/facebook

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How do I get a list of Facebook events for a city with an API?
- Is there an API for local event discovery on Facebook?
- How do I get full Facebook event details for a city feed in one call?