Social platforms

Get a Facebook post or Reel by URL · Facebook API

GET/facebook/posts
$min $0.003

Returns one public Facebook post or Reel by its URL: author, text, media, music and reaction, comment and share counts. Set `include_comments` or `include_transcript` for a comment sample or a video transcript. Returns `not_found` when the post does not exist or is not public.

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

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

Parameters

urlqueryrequired
Public permalink to the Facebook post or reel.
include_commentsquery
When true, includes a sample of top-level comments when available.
include_transcriptquery
When true, includes a plain-text transcript when available for the video.
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

  • Fetch canonical public Facebook content for summarization, ranking, monitoring, or enrichment.
  • Attach engagement, author, media, and source metadata to an agent workflow.
  • 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

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.

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 in the data object

A successful Get a Facebook post or Reel by URL call returns one data object with these fields (12 of 18 shown — the docs list the full schema).

platformstring | null
Social platform for this content. One of: facebook.
post_idstring | null
Platform post id when available.
urlstring | null
Canonical or resolved public URL for this post or reel.
descriptionstring | null
Caption or body text when available.
published_atnumber | null
Publication timestamp in ISO 8601 when available. Unix seconds.
is_paid_partnershipboolean | null
Whether the post is labelled as a paid partnership. Null or omitted when Facebook does not say.
feedback_idstring | null
Opaque feedback identifier when exposed by the platform; may be used for related lookups.
link_attachmentobject | null
Link preview for posts that share an external link. Null when the post has no link attachment.
authorobject | null
Author when found.
like_countnumber | null
Like count when available.
comment_countnumber | null
Comment count when available.
share_countnumber | null
Share count when available.
Related endpoints

More Facebook operations

Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.