Social platforms

Search Facebook events · Facebook API

GET/facebook/events/search
$min $0.003

Returns public Facebook events whose name matches a query, with dates, place and attendance. Paginate with `cursor`.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/facebook/events/search?query= \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

queryqueryrequired
Search query text for Facebook events by name.
cursorquery
Opaque pagination cursor from a previous response's `pagination.next_cursor`. Omit for the first page.
The parameter for this Facebook operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the Facebook API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs Facebook public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Search Facebook for public mentions, creators, posts, or topics matching a user query.
  • Feed ranked Facebook results into research, monitoring, and enrichment workflows.
  • Give an AI agent a stable Facebook data source without building a per-platform integration.
  • Normalize Facebook responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields on each record in data

A successful Search Facebook events call returns data as an array; each record carries these fields (12 of 14 shown — the docs list the full schema).

idstring | null
Stable Facebook event identifier.
urlstring | null
Canonical public event URL when available.
namestring | null
Event name.
day_time_sentencestring | null
Human-readable date and time label when available.
start_atnumber | null
Event start time as an ISO-8601 timestamp when available. Unix seconds.
is_onlineboolean | null
Whether the event is online when available.
is_pastboolean | null
Whether the event has already ended when available.
event_kindstring | null
Event visibility kind when available, such as public or private.
placeobject | null
Venue or place associated with the event.
coverobject | null
Cover image for the event.
price_rangestring | null
Ticket price range label when available.
interested_countnumber | null
Number of people marked interested when available.