Facebook Post details API

Request parameters

Code samples

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "facebook",
  "action": "post",
  "params": {
    "url": "https://www.facebook.com/nasa"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

{
  "id": "req_…",
  "platform": "facebook",
  "action": "post",
  "results": {
    "id": "（已隐去）",
    "url": "https://www.facebook.com/NASA/posts/pfbid02FDWE6z2u4MfbHnirq8BdWUYtYi1cdDNEiayPTquFJDjCKi92ULJoWM5Q3U7e94Ddl",
    "text": "Welcome to the Artemis Accords, San Marino 🇸🇲\n\nSan Marino has joined 75 other nations by committing to the safe and sustainable exploration of space. https://go.nasa.gov/4iKdyyL",
    "author_name": "（已隐去）",
    "like_count": 484,
    "comment_count": 103,
    "share_count": 55,
    "posted_at": "2026-09-25T20:31:03+00:00",
    "platform": "facebook"
  },
  "billing": { … },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

Per-minute request limit reached. Wait for Retry-After and try again.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

• Facebook Official: Public Visibility of Page Profiles, Posts, and Comments ↗

  Official Meta documentation discusses public details across Pages, profiles, posts, and comments; this definition of visibility does not guarantee that every URL can be read, that every field will be returned, or that this endpoint holds Meta access authorization.

  Checked 2026-09-04

• Meta Official Documentation: Automated Data Collection Requires Prior Permission ↗

  Meta explicitly states that automated collection of Facebook data without prior permission violates its terms, even for publicly visible data. Citing authoritative sources does not constitute proof of authorization for platform collection or reuse.

  Checked 2026-09-04