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

> Returns upcoming and past events for a public Facebook page. Each row carries the event title, the permalink, the start time, the host page's name, and on `post.ext.event` the rendered time line (`time_text`, e.g. "Fri, Sep 11 at 5:00 PM CDT"), `location_name` (the venue), `city`, `start_timestamp`, and the `is_canceled`, `is_past` and `is_online` flags. `published_at` on this lane is the event's START time, not a publication time, so it is routinely in the FUTURE on an upcoming event. The page's event listing carries no cover image, no description and no RSVP counts, so on a plain call `post.content.thumbnail_url`, `post.engagement.views` and `post.engagement.likes` are null. Send `include=details` and every event is joined, in the same call, to the per-event details lookup: the description, the street address, the coordinates, the hosts (`hosts[]` and the one-line `host_context_text`), the category, the privacy, the attendance count, the cover image and the RSVP counts land on each row. An event has no views or likes, so `engagement.views` then carries the interested count and `engagement.likes` the going count, with the same numbers under their real names on `post.ext.event.interested_count` and `going_count`. Values the row already carried (its shorter time line, its city) are never replaced. Cost: 1 credit for the page plus 1 credit per event filled from a fresh lookup (8 events a page, so 9 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 6 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. Forward the returned cursor for additional pages.

TL;DR: `GET /v1/facebook/profile/events` costs 1 credit for the page. include=details holds 1 credit per event (8 a page) and keeps only the rows filled from a fresh lookup, so a page is at most 9 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 public Facebook page. |
| `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`, `latitude`, `longitude`, `hosts`, `host_context_text`, `category`, `privacy`, `attendance_count`, `interested_count` and `going_count`, the cover image on `post.content.thumbnail_url`, and the RSVP counts on `post.engagement.views` (interested) and `.likes` (going). Holds 1 credit per event (8 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 9 credits. The join takes 2 to 6 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/profile/events" \
  --data-urlencode "url=https://www.facebook.com/brickyardoldtown" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

### What is the Facebook page events API?

GET /v1/facebook/profile/events lists all events hosted by a Facebook page. Pass the page url and each event comes back with its name, the start time, the rendered time line, the venue, the city, and the cancelled, past, and online flags. It costs 1 credit per call.

### What do I pass to identify the page?

Pass the page's Facebook URL in the url param. The endpoint reads that page's events tab and returns the structured list, so you can track a venue, brand, or organizer's upcoming events without opening a browser.

### How do I page through the full event list?

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

### How is this different from the city events endpoint?

/v1/facebook/events lists events for a city, while profile/events lists the events for one specific page. Use this to monitor a single venue or organizer's calendar over time.

### How much does it cost?

Each call is 1 credit on the standard tier. New accounts start with 100 free credits and no card, so you can wire up a page's event calendar and test it before spending.

### Do I get the description, address, and RSVP counts?

Not on a plain call. A page's events tab carries the title, the start, the venue, the city, and the status flags, and nothing deeper. Add include=details and each event is joined to its own record in the same call, filling the description, the street address, the coordinates, the hosts, the category, the privacy, the attendance count, the cover image, and the interested and going counts. The page is 1 credit plus 1 credit per event filled from a fresh lookup, 9 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 list a Facebook page's events with an API?
- How do I monitor a venue or organizer's Facebook events?
- How do I get Facebook page event descriptions and RSVP counts in one call?