Facebook Profile Events API
Scrape Facebook Profile Events data with one API call. 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.
Last updated October 2026Maintained by the SocialCrawl team
Returns a Facebook page's upcoming and past events, each with a title, link, the start time, the venue, the city, the rendered time line, and the cancelled, past and online flags.
Use it for one page's own events; events covers a city. The start time sits on published_at and is often in the future. Optional include=details adds the description, hosts, cover and RSVP counts.
Searching 68 platforms in parallel
TikTok·
Instagram·
YouTube·Facebook·
X·
LinkedIn·
Reddit·
Threads·
Pinterest·
Twitch·
Truth Social·
Snapchat·
Kick·
Bluesky·
Kwai·
Rumble·
Spotify·
Apple Music·TikTok Shop·
Amazon Shop·
Google Shopping·
Trustpilot·
TripAdvisor·
Yelp·
Linktree·
Komi·
Pillar·
lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·
Finance·
Polymarket·
Tavily·
Hacker News·
GitHub·
Perplexity·
Naver·
Utility·
Universal SearchTikTok·Instagram·YouTube·Facebook·X·LinkedIn·Reddit·Threads·Pinterest·Twitch·Truth Social·Snapchat·Kick·Bluesky·Kwai·Rumble·Spotify·Apple Music·TikTok Shop·Amazon Shop·Google Shopping·Trustpilot·TripAdvisor·Yelp·Linktree·Komi·Pillar·lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Finance·Polymarket·Tavily·Hacker News·GitHub·Perplexity·Naver·Utility·Universal SearchTikTok·Instagram·YouTube·Facebook·X·LinkedIn·Reddit·Threads·Pinterest·Twitch·Truth Social·Snapchat·Kick·Bluesky·Kwai·Rumble·Spotify·Apple Music·TikTok Shop·Amazon Shop·Google Shopping·Trustpilot·TripAdvisor·Yelp·Linktree·Komi·Pillar·lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Finance·Polymarket·Tavily·Hacker News·GitHub·Perplexity·Naver·Utility·Universal SearchTikTok·Instagram·YouTube·Facebook·X·LinkedIn·Reddit·Threads·Pinterest·Twitch·Truth Social·Snapchat·Kick·Bluesky·Kwai·Rumble·Spotify·Apple Music·TikTok Shop·Amazon Shop·Google Shopping·Trustpilot·TripAdvisor·Yelp·Linktree·Komi·Pillar·lnk.bio·Facebook Ads·Google Ads·LinkedIn Ads·Google Search·Google News·Finance·Polymarket·Tavily·Hacker News·GitHub·Perplexity·Naver·Utility·Universal SearchWhat can you do with the Profile Events API?
The Profile Events endpoint gives you structured Facebook data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/facebook/profile/events?url=https%3A%2F%2Fwww.facebook.com%2Fbrickyardoldtown"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/facebook/profile/events",
params={
'url': 'https://www.facebook.com/brickyardoldtown',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/facebook/profile/events?url=https%3A%2F%2Fwww.facebook.com%2Fbrickyardoldtown",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();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`. |
What does the Facebook Profile Events API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "facebook",
"endpoint": "/v1/facebook/profile/events",
"data": {
"items": [
{
"post": {
"id": "1824704508673350",
"url": "https://www.facebook.com/events/1824704508673350/",
"content": {
"text": "Sample comment text (redacted).",
"media_urls": null,
"thumbnail_url": null,
"duration_seconds": null
},
"author": {
"username": null,
"display_name": "user_d8b6c8",
"avatar_url": null,
"verified": null
},
"engagement": {
"views": null,
"likes": null,
"comments": null,
"shares": null,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": null,
"deleted": false
},
"published_at": "2026-10-02T22:30:00.000Z",
"ext": {
"author_id": "user_31473f",
"published_at_epoch": 1790980200,
"event": {
"time_text": "Fri, Oct 2 at 5:30 PM CDT",
"is_canceled": false,
"is_past": false,
"is_online": false,
"location_name": "Brickyard",
"city": "Wichita",
"start_timestamp": 1790980200
}
}
},
"computed": {
"engagement_rate": null,
"language": null,
"content_category": "other",
"estimated_reach": null
}
},
{
"post": {
"id": "2442231312923237",
"url": "https://www.facebook.com/events/2442231312923237/",
"content": {
"text": "Sample comment text (redacted).",
"media_urls": null,
"thumbnail_url": null,
"duration_seconds": null
},
"author": {
"username": null,
"display_name": "user_d8b6c8",
"avatar_url": null,
"verified": null
},
"engagement": {
"views": null,
"likes": null,
"comments": null,
"shares": null,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": null,
"deleted": false
},
"published_at": "2026-10-03T01:00:00.000Z",
"ext": {
"author_id": "user_31473f",
"published_at_epoch": 1790989200,
"event": {
"time_text": "Fri, Oct 2 at 8:00 PM CDT",
"is_canceled": false,
"is_past": false,
"is_online": false,
"location_name": "Brickyard",
"city": "Wichita",
"start_timestamp": 1790989200
}
}
},
"computed": {
"engagement_rate": null,
"language": null,
"content_category": "other",
"estimated_reach": null
}
}
],
"next_cursor": "eyJpZCI6IllYQndYMk52Ykd4bFkzUnBiMjQ2Y0daaWFXUXdNak51YnpVeldrZFJOVXM0UWtaVk5UUklhRmg2TVZwbU5FSlhNa3RNVUhCTmFtVnhaMkZGU2xsVVpYaElTa2czVlVob01YZFFaWFpUTjFCSVFsUTBOakZ5VUhKd04xZzNUVkY1WWpSRU0wZEZWbk5uT1haRWVXdFpVMFV6UVZOcyIsImN1cnNvciI6IkFRSFQ4cUtoRjJDTnVjY3FiVmJONTk0NFY5XzNTQ1Rud0NNX1o0NmVNeXl3eWJ0eTcxY3ZHS0dWclA5LVdDUGt6QS04ckhhZXI1QTdxYUZHTktWOXg5WGlqUSJ9",
"total": 11,
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiZXlKcFpDSTZJbGxZUW5kWU1rNTJZa2Q0YkZrelVuQmlNalEyWTBkYWFXRlhVWGROYWs1MVlucFZlbGRyWkZKT1ZYTTBVV3RhVms1VVVrbGhSbWcyVFZad2JVNUZTbGhOYTNSTlZVaENUbUZ0Vm5oYU1rWkdVMnhzVlZwWWFFbFRhMmN6VmxWb2IwMVlaRkZhV0ZwVVRqRkNTVkZzVVRCT2FrWjVWVWhLZDA0eFp6TlVWa1kxV1dwU1JVMHdaRVpXYms1dVQxaGFSV1ZYZEZwVk1GVjZVVlpPY3lJc0ltTjFjbk52Y2lJNklrRlJTRlE0Y1V0b1JqSkRUblZqWTNGaVZtSk9OVGswTkZZNVh6TlRRMVJ1ZDBOTlgxbzBObVZOZVhsM2VXSjBlVGN4WTNaSFMwZFdjbEE1TFZkRFVHdDZRUzA0Y2toaFpYSTFRVGR4WVVaSFRrdFdPWGc1V0dscVVTSjkiLCJlIjoiZmFjZWJvb2svcHJvZmlsZS9ldmVudHMiLCJwIjoiY3Vyc29yIn0",
"has_more": true,
"page_size": 8
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T07:32:35.661Z",
"redacted": true
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Facebook Profile Events API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 68 platforms covering 10B+ monthly active users.
One schema, every platform
Query 68 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usWhat is the Facebook page events API?
What do I pass to identify the page?
How do I page through the full event list?
How is this different from the city events endpoint?
How much does it cost?
Do I get the description, address, and RSVP counts?
Ask AI about SocialCrawl
Ready to scrape Facebook Profile Events data?
Get your API key and start pulling Facebook data in under 60 seconds.