# Facebook Group Events API (https://www.socialcrawl.dev/platforms/facebook/group-events) > Returns the upcoming events of a public Facebook group, the same list a logged-out visitor sees on the group's Events tab. Pass the group `url` (the group URL or its Events tab URL, with the numeric id or the vanity name) or `group_id`. Each row carries the event id, the title (`content.text`), the permalink, and on `post.ext.event.time_text` the short time line (e.g. "Mon, 16 Nov at 18:00 EST"). The group listing sends no timestamp, venue, host, cover image or RSVP counts, so on a plain call `published_at`, `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 start (`published_at` and `post.ext.event.start_timestamp`, the event's START time, so routinely in the future), the description, the venue (`location_name`, `address`, `city`, `latitude`, `longitude`, and `location_type` with `location_id` when the venue is a Facebook Page), the hosts, 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`. Past events are not available here: the group listing this endpoint reads carries upcoming events only. A group whose Events tab needs a login returns an empty list, and a page's own events are `/v1/facebook/profile/events`. A page held 1 to 3 events on the groups measured; forward `pagination.next_cursor` as `cursor` while `pagination.has_more` is true, and expect the last cursor to answer an empty page, at 0 credits. Cost: 1 credit for the page plus 1 credit per event filled from a fresh lookup (at most 8 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. TL;DR: `GET /v1/facebook/group/events` costs 1 credit for the page. include=details holds 1 credit per event (at most 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` | no | Full URL of the public Facebook group, or of its Events tab (`https://www.facebook.com/groups//events`). | | `group_id` | no | The group's numeric id or its vanity name. | | `cursor` | no | Cursor to get the next page of events. Take it from `pagination.next_cursor` on the previous response. | | `include` | no | Set to `details` (one token only) to fill, on every event in this one call, `published_at` and `post.ext.event.start_timestamp`, `description`, `location_name`, `address`, `city`, `latitude`, `longitude`, `location_type`, `location_id`, `hosts`, `host_context_text`, `category`, `privacy`, `is_online`, `is_canceled`, `attendance_count`, `interested_count` and `going_count`, the cover image on `post.content.thumbnail_url`, the host line on `post.author.display_name`, and the RSVP counts on `post.engagement.views` (interested) and `.likes` (going). Holds 1 credit per event (at most 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/group/events" \ --data-urlencode "url=https://www.facebook.com/groups/YorkRoadRunnersClub" \ -H "x-api-key: sc_YOUR_API_KEY" ``` ## FAQ ### What does the Facebook Group Events API return? Returns a public Facebook group's upcoming events, each with the event id, title, link and a short time line. The response uses the same JSON envelope as every SocialCrawl endpoint, with the data, credits_used and request_id fields. ### When should I use the Facebook Group Events endpoint? Use it for a group's events; profile/events covers a page and events a city. Optional include=details adds the start time, venue, hosts, cover and RSVP counts. ### How much does the Facebook Group Events API cost? The price depends on the request, from 1 to 9 credits per call. Every new account gets 100 free credits. Credits for failed or empty calls are refunded automatically, and there is no subscription. ### What parameters does the Facebook Group Events API need? Identify the target with one of url, group_id. It also accepts 9 optional parameters, all listed on this page. ### How do I call the Facebook Group Events API? Send a GET request to https://www.socialcrawl.dev/v1/facebook/group/events?url=https%3A%2F%2Fwww.facebook.com%2Fgroups%2FYorkRoadRunnersClub with your API key in the x-api-key header. An Authorization: Bearer header works too. 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: - What does the SocialCrawl Facebook Group Events API return? - How do I get Facebook Group Events data with the SocialCrawl API?