Facebook Profile Events API
API 한 번의 호출로 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.
2026년 10월 업데이트SocialCrawl 팀이 직접 관리해요
Facebook 페이지의 예정 이벤트와 지난 이벤트를 돌려줍니다. 제목과 링크, 시작 시각, 장소 이름, 도시, 날짜 문구, 취소와 종료, 온라인 여부가 담깁니다.
한 페이지가 직접 여는 행사만 볼 때 사용하세요. 도시 전체 목록은 events를 쓰세요. 시작 시각이 published_at 자리에 들어가 앞날 날짜가 나옵니다. 설명과 주소, 주최자, 커버 이미지, 응답 수는 include=details를 붙여야 채워집니다.
68개 플랫폼을 병렬로 검색합니다
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 SearchProfile Events API로 무엇을 할 수 있을까요
Profile Events 엔드포인트가 통합 스키마와 계산 필드를 담은 Facebook 데이터를 한 번의 요청으로 보내드려요. 스크래핑 인프라를 직접 만들거나 유지할 필요가 없어요.
요청 예시
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();파라미터
| 파라미터 | 필수 | 설명 |
|---|---|---|
| url | 예 | Full URL of the public Facebook page. |
| cursor | 아니오 | Cursor returned by the previous response for pagination. |
| include | 아니오 | 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 | 아니오 | 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 | 아니오 | 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`. |
Facebook Profile Events API는 무엇을 돌려주나요
모든 응답은 하나의 통합 스키마를 따라요. 크레딧을 쓰기 전에 어떤 필드가 돌아오는지, 실제 응답 본문 그대로 확인해 보세요.
응답 예시 보기
{
"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
}통합 응답 구조를 보여 주는 실제 샘플이에요. 필드 값은 조회한 대상에 따라 달라져요.
Facebook Profile Events API는 어떻게 동작하나요
API 키와 함께 GET 요청을 보내면, 통합 스키마와 계산 필드를 담은 깔끔한 JSON이 돌아와요.
메서드
GET
응답 형식
JSON
소셜 미디어 데이터를 몇 초 만에 수집하는 방법
개발자를 위한 가장 빠른 소셜 미디어 스크래핑 API. 월간 활성 사용자 100억 명 이상을 포괄하는 68개 플랫폼에서 프로필, 게시물, 댓글, 분석 데이터를 수집하세요.
모든 플랫폼을 하나의 스키마로
동일한 응답 구조로 68개 플랫폼을 조회하세요. 연동은 한 번이면 충분합니다.
단순 수집을 넘어 계산된 필드 제공
엔드포인트가 해당 지표를 지원하고 계산에 필요한 원본 값이 있을 때, 정규화된 레코드에 engagement_rate, estimated_reach, content_category, language를 함께 담아 바로 활용할 수 있습니다.
코드 한 줄 쓰기 전에, 데이터부터
Visual Data Explorer에 URL만 붙여넣으면 결과 카드와 정형화된 테이블, CSV 내보내기를 바로 사용할 수 있습니다.
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"
}
}
}자주 묻는 질문
API, 요금제, 기능에 대한 질문과 답변입니다.
문의하기Facebook 페이지 이벤트 API는 뭔가요?
페이지는 무엇으로 지정하나요?
전체 이벤트 목록은 어떻게 페이지네이션하나요?
도시 이벤트 엔드포인트와 뭐가 다른가요?
비용은 얼마인가요?
설명과 주소, 참석 인원도 함께 오나요?
AI에게 SocialCrawl을 물어보세요
Facebook Profile Events 데이터, 가져올 준비 되셨어요?
API 키 받고 60초 안에 Facebook 데이터를 받아 가세요.