Facebook data product

Facebook data for pages, posts, video, and reporting.

Verification pending

Give agencies and buyers governed inputs for page diligence and content reporting, with bounded collection and buyer-visible usage receipts.

Buyer evidence pendingAccess follows the canonical catalog evidence decision.

Designed product surface

Useful scope, explicit boundaries.

These capabilities describe the intended product contract. They do not override the status shown above.

Pages and profiles

Public page and profile inputs for account research.

Posts and video

Content and performance signals with explicit record caps.

Reviews

Public review inputs where the product-specific contract supports them.

AI intelligence

Deterministic analysis with a separate premium usage receipt.

The API Aha difference

Every product must ship with proof.

API management is not a catalog of optimistic endpoint names. The response contract, cache behavior, usage math, and buyer path are part of the product.

IdentityOne channel-specific buyer identity; no duplicate hidden API key.

SemanticsCorrect HTTP status plus an assertion that the requested data is present.

FreshnessA visible collection or cache timestamp and bounded sample.

UsageSuccessful responses disclose the units and formula applied.

Canonical product status

Underlying families stay visible.

This page describes the governed product surface. Access stays closed until the linked product families retain current authenticated cold and warm semantic, cache, and billing receipts.

Social

Facebook Intelligence

The current repository does not retain a complete, current authenticated-subscriber cold/warm receipt for every buyer-visible operation. API Aha does not present this family as available yet.

Review evidence →

Need this workflow?

Ask for the evidence plan.

We will not substitute a sales promise for a missing product receipt.

Contact API Aha