Profile › Events
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.
Metered: 10–90 credits. We reserve the ceiling when the call starts and charge what it actually used when it finishes.
Paginates by cursor: see Pagination.
Request
- Base URL: https://api.insightsocial.app
- URL: https://api.insightsocial.app/v1/facebook/profile/events
- Auth: API key in header x-api-key
Query parameters
Full URL of the public Facebook page.
Cursor returned by the previous response for pagination.
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). Without it the call is unchanged.
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.
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.
Set to 1 to get the price of this call without making it: data.dry_run carries credits_min and credits_max. Nothing is charged.
Response
Success.
Changes
No recorded changes to this operation across all 1 revision of this API.