Facebook data, ready when you are.

Pages, posts, reels, comments, reviews, ads, events and marketplace listings from Facebook.

Try in playground From $0.0022 a record · $0.10 free

What you can get.

  • $0.009per record

    Pages

    Page cards for up to ten pages by URL or handle. Followers, likes, talking-about, reviews and recommend %, category, contact, hours, ads status, social links.

    Try it →
  • $0.0045per record

    Posts by a person

    A person's latest posts, with likes and comments.

    Try it →
  • $0.0045per record

    Reels

    Recent reels of a page. Plays, audio, duration, video links.

    Try it →
  • $0.0022per record

    Comments

    Comments on up to five posts, reels or photos by permalink.

    Try it →
  • $0.0022per record

    Reviews

    Reviews/recommendations on up to five pages.

    Try it →
  • $0.0067per record

    Followers

    The followers OR following of up to three pages. Name, profile URL, bio. The dearest rows in the catalogue.

    Try it →
  • $0.0045per record

    Ads

    Every ad a page runs in Meta's Ad Library. Creative, headline, CTA, link, dates, platforms, advertiser and EU reach.

    Try it →
  • $0.009per record

    Events

    Events by keyword. Name, date, venue, host, going/interested, tickets.

    Try it →
  • $0.009per record

    Marketplace

    Marketplace listings from a category or search URL. Title, price, condition, location, attributes, photos.

    Try it →

What the data looks like.

pageNameusernamecategoryfollowerslikesrecommendPercentreviewCountphonewebsiteaddressrunningAdspageKeypageIdpageUrladdressMapUrlprofilePictureUrlcoverPhotoUrlpageCreatedadLibraryIdprofilePhotoLinkdetails
Brewlab CoffeebrewlabcoffeeCoffee shop21,40019,80096412+1 512-555-0142https://brewlab.example210 Congress Ave, Austin, TXtruebrewlab-coffee2264557836https://www.facebook.com/brewlab-coffee-1000https://www.facebook.com/brewlab-coffee-1000https://img.facebook.com/brewlab-coffee.jpghttps://img.facebook.com/brewlab-coffee.jpg2026-10-041810680602https://img.facebook.com/brewlab-coffee.jpg
  • {}
NorthfoldnorthfoldhqSoftware company8,4007,900null0nullhttps://northfold.exampleLondon, United Kingdomtruenorthfold4116075838https://www.facebook.com/northfold-1001https://www.facebook.com/northfold-1001https://img.facebook.com/northfold.jpghttps://img.facebook.com/northfold.jpg2026-10-133667530691https://img.facebook.com/northfold.jpg
  • {}
Casa Lumen TacoscasalumentacosMexican restaurant41,20039,100941,210+1 619-555-0190https://casalumen.example88 Harbor Dr, San Diego, CAfalsecasa-lumen-tacos4086272717https://www.facebook.com/casa-lumen-tacos-1002https://www.facebook.com/casa-lumen-tacos-1002https://img.facebook.com/casa-lumen-tacos.jpghttps://img.facebook.com/casa-lumen-tacos.jpg2026-10-12741587832https://img.facebook.com/casa-lumen-tacos.jpg
  • {}
21 fields, scroll sideways for all. Example rows: made-up names, real field names. Live calls return real data.

For developers

API reference.

One endpoint, POST /v1/facebook. Open an operation to see its fields.

Read the docs
Pagespages

Page cards for up to ten pages by URL or handle. Followers, likes, talking-about, reviews and recommend %, category, contact, hours, ads status, social links.

FieldTypeMeaning
subjects *list of string · 1-10 itemsPage URLs or vanity handles.

Response fields, each row of data

FieldType
pageKeystring
pageIdstring
pageUrlstring
pageNamestring
usernamestring
categorystring
introstring
followersinteger
likesinteger
followinginteger
talkingAboutinteger
wereHereinteger
reviewCountinteger
recommendPercentnumber
phonestring
emailstring
websitestring
otherWebsiteslist of string
addressstring
addressMapUrlstring
businessHoursany
priceRangestring
servicesstring
profilePictureUrlstring
coverPhotoUrlstring
pageCreatedstring
confirmedOwnerstring
runningAdsboolean
adLibraryIdstring
socialLinksany
personalProfileboolean
profilePhotoLinkstring
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · pages
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"pages","subjects":["nike","natgeo"]}'

Example response rows

data · made-up names, real field names
[
  {
    "pageName": "Brewlab Coffee",
    "username": "brewlabcoffee",
    "category": "Coffee shop",
    "followers": 21400,
    "likes": 19800,
    "recommendPercent": 96,
    "reviewCount": 412,
    "phone": "+1 512-555-0142",
    "website": "https://brewlab.example",
    "address": "210 Congress Ave, Austin, TX",
    "runningAds": true,
    "pageKey": "brewlab-coffee",
    "pageId": "2264557836",
    "pageUrl": "https://www.facebook.com/brewlab-coffee-1000",
    "addressMapUrl": "https://www.facebook.com/brewlab-coffee-1000",
    "profilePictureUrl": "https://img.facebook.com/brewlab-coffee.jpg",
    "coverPhotoUrl": "https://img.facebook.com/brewlab-coffee.jpg",
    "pageCreated": "2026-10-04",
    "adLibraryId": "1810680602",
    "profilePhotoLink": "https://img.facebook.com/brewlab-coffee.jpg",
    "details": {}
  },
  {
    "pageName": "Northfold",
    "username": "northfoldhq",
    "category": "Software company",
    "followers": 8400,
    "likes": 7900,
    "recommendPercent": null,
    "reviewCount": 0,
    "phone": null,
    "website": "https://northfold.example",
    "address": "London, United Kingdom",
    "runningAds": true,
    "pageKey": "northfold",
    "pageId": "4116075838",
    "pageUrl": "https://www.facebook.com/northfold-1001",
    "addressMapUrl": "https://www.facebook.com/northfold-1001",
    "profilePictureUrl": "https://img.facebook.com/northfold.jpg",
    "coverPhotoUrl": "https://img.facebook.com/northfold.jpg",
    "pageCreated": "2026-10-13",
    "adLibraryId": "3667530691",
    "profilePhotoLink": "https://img.facebook.com/northfold.jpg",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try pages in the playground Examples and pricing for pages
Posts by a personposts

Recent posts of a page, profile or group. Text, reactions by type, comments, shares, views, media, mentions, top comments.

FieldTypeMeaning
subject *string · ≤400 charsOne page, profile or group URL or handle.
sincestring · YYYY-MM-DD
untilstring · YYYY-MM-DD
limitinteger · 1-100

Response fields, each row of data

FieldType
postUrlstring
postIdstring
authorKeystring
authorany
textstring
postedAtstring
contentTypestring
reactionsinteger
reactionBreakdownany
commentsinteger
sharesinteger
viewsinteger
mediaany
videoDurationstring
hashtagslist of string
mentionslist of string
linkPreviewany
sourceany
topCommentsany
collaboratorsany
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · posts
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"posts","subject":"nike","since":"2026-10-01","limit":20}'

Example response rows

data · made-up names, real field names
[
  {
    "author": "Brewlab Coffee",
    "text": "New autumn menu is here 🍂",
    "postedAt": "2026-10-14T15:00:00Z",
    "contentType": "photo",
    "reactions": 1240,
    "comments": 86,
    "shares": 41,
    "views": null,
    "postUrl": "https://www.facebook.com/brewlab-coffee-1000",
    "postId": "3422847386",
    "authorKey": "3628227038",
    "details": {}
  },
  {
    "author": "Brewlab Coffee",
    "text": "Latte art night on the 24th, free entry.",
    "postedAt": "2026-10-10T18:00:00Z",
    "contentType": "event",
    "reactions": 610,
    "comments": 44,
    "shares": 58,
    "views": null,
    "postUrl": "https://www.facebook.com/brewlab-coffee-1001",
    "postId": "3041163862",
    "authorKey": "1879076958",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try posts by a person in the playground Examples and pricing for posts by a person
Reelsreels

Recent reels of a page. Plays, audio, duration, video links.

FieldTypeMeaning
subject *string · ≤400 charsOne page URL or handle.
limitinteger · 1-100

Response fields, each row of data

FieldType
reelIdstring
reelUrlstring
playsinteger
playsLabelstring
publishedAtstring
durationSecnumber
audioTitlestring
audioArtiststring
audioTrackstring
audioTrackIdstring
audioTypestring
audioMutedboolean
remixableboolean
videoUrlstring
thumbnailUrlstring
dimensionsstring
captionLanguageslist of string
dubbedAudioLanguageslist of string
captionsFileUrlstring
pageany
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · reels
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"reels","subject":"natgeo","limit":10}'

Example response rows

data · made-up names, real field names
[
  {
    "plays": 184000,
    "playsLabel": "184K",
    "durationSec": 22,
    "audioTitle": "Original audio",
    "audioArtist": "Brewlab Coffee",
    "publishedAt": "2026-10-13",
    "remixable": true,
    "reelId": "2312965674",
    "reelUrl": "https://www.facebook.com/item-1000",
    "audioTrackId": "256678523",
    "videoUrl": "https://www.facebook.com/item-1000",
    "thumbnailUrl": "https://img.facebook.com/item.jpg",
    "captionsFileUrl": "https://www.facebook.com/item-1000",
    "details": {}
  },
  {
    "plays": 96000,
    "playsLabel": "96K",
    "durationSec": 31,
    "audioTitle": "Autumn Lo-fi",
    "audioArtist": "Sundays",
    "publishedAt": "2026-10-09",
    "remixable": true,
    "reelId": "3547752111",
    "reelUrl": "https://www.facebook.com/item-1001",
    "audioTrackId": "546944639",
    "videoUrl": "https://www.facebook.com/item-1001",
    "thumbnailUrl": "https://img.facebook.com/item.jpg",
    "captionsFileUrl": "https://www.facebook.com/item-1001",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try reels in the playground Examples and pricing for reels
Commentscomments

Comments on up to five posts, reels or photos by permalink.

FieldTypeMeaning
subjects *list of string · 1-5 itemsPost, reel or photo permalinks.
includeRepliesbooleanfalse: top-level comments only; true (default) also returns the replies nested under them.
sortenumtop = Facebook's "most relevant"; threaded = all comments in thread order.top · threaded · newest
limitinteger · 1-100

Response fields, each row of data

FieldType
commentUrlstring
commentTextstring
commenterstring
commenterIdstring
commenterUrlstring
commenterPicturestring
likesinteger
repliesinteger
replyDepthinteger
isReplyboolean
replyingTostring
threadRootAuthorstring
commentDatestring
commentMediaTypestring
commentMediaUrlstring
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · comments
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"comments","subjects":["https://www.facebook.com/nike/posts/<post-id>"],"sort":"top","limit":50}'

Example response rows

data · made-up names, real field names
[
  {
    "commenter": "Ravi Kumar",
    "commentText": "Can't wait to try the pumpkin latte!",
    "likes": 24,
    "replies": 2,
    "commentDate": "2026-10-14",
    "isReply": false,
    "replyDepth": 0,
    "replyingTo": null,
    "commentUrl": "https://www.facebook.com/ravi-kumar-1000",
    "commenterId": "1050942139",
    "commenterUrl": "https://www.facebook.com/ravi-kumar-1000",
    "commentMediaUrl": "https://www.facebook.com/ravi-kumar-1000",
    "details": {}
  },
  {
    "commenter": "Lena Müller",
    "commentText": "Are you open on Sunday?",
    "likes": 6,
    "replies": 1,
    "commentDate": "2026-10-14",
    "isReply": false,
    "replyDepth": 0,
    "replyingTo": null,
    "commentUrl": "https://www.facebook.com/lena-m-ller-1001",
    "commenterId": "455822143",
    "commenterUrl": "https://www.facebook.com/lena-m-ller-1001",
    "commentMediaUrl": "https://www.facebook.com/lena-m-ller-1001",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try comments in the playground Examples and pricing for comments
Reviewsreviews

Reviews/recommendations on up to five pages.

FieldTypeMeaning
subjects *list of string · 1-5 itemsPage URLs or vanity handles.
limitinteger · 1-100

Response fields, each row of data

FieldType
reviewIdstring
reviewUrlstring
reviewTextstring
recommendedboolean
reviewDatestring
reviewerNamestring
reviewerAvatarstring
reviewerProfileUrlstring
likesinteger
commentCountinteger
photoslist of string
tagsstring
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · reviews
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"reviews","subjects":["starbucks"],"limit":25}'

Example response rows

data · made-up names, real field names
[
  {
    "reviewerName": "Hannah Wright",
    "recommended": true,
    "reviewText": "Friendly staff and great coffee.",
    "reviewDate": "2026-10-11",
    "likes": 3,
    "commentCount": 0,
    "reviewId": "309363717",
    "reviewUrl": "https://www.facebook.com/hannah-wright-1000",
    "reviewerProfileUrl": "https://www.facebook.com/hannah-wright-1000",
    "photos": [
      "https://img.facebook.com/hannah-wright.jpg"
    ],
    "details": {}
  },
  {
    "reviewerName": "Arjun Shah",
    "recommended": true,
    "reviewText": "My favourite spot to work from.",
    "reviewDate": "2026-10-02",
    "likes": 1,
    "commentCount": 1,
    "reviewId": "3649534047",
    "reviewUrl": "https://www.facebook.com/arjun-shah-1001",
    "reviewerProfileUrl": "https://www.facebook.com/arjun-shah-1001",
    "photos": [
      "https://img.facebook.com/arjun-shah.jpg"
    ],
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try reviews in the playground Examples and pricing for reviews
Followersfollowers

The followers OR following of up to three pages. Name, profile URL, bio. The dearest rows in the catalogue.

FieldTypeMeaning
subjects *list of string · 1-3 itemsPage URLs or vanity handles.
directionenumfollowers · following
limitinteger · 1-100

Response fields, each row of data

FieldType
profileIdstring
followerNamestring
profileUrlstring
avatarUrlstring
biostring
relationshipstring
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · followers
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"followers","subjects":["natgeo"],"direction":"following","limit":25}'

Example response rows

data · made-up names, real field names
[
  {
    "followerName": "Ravi Kumar",
    "bio": "Coffee and cycling",
    "relationship": "follower",
    "profileId": "624155740",
    "profileUrl": "https://www.facebook.com/ravi-kumar-1000",
    "avatarUrl": "https://img.facebook.com/ravi-kumar.jpg",
    "details": {}
  },
  {
    "followerName": "Lena Müller",
    "bio": "Designer in Austin",
    "relationship": "follower",
    "profileId": "3527258922",
    "profileUrl": "https://www.facebook.com/lena-m-ller-1001",
    "avatarUrl": "https://img.facebook.com/lena-m-ller.jpg",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try followers in the playground Examples and pricing for followers
Adsads

Every ad a page runs in Meta's Ad Library. Creative, headline, CTA, link, dates, platforms, advertiser and EU reach.

FieldTypeMeaning
subjects *list of string · 1-5 itemsPage URLs or vanity handles.
statusenum"active": ads running now; "inactive": ads that have stopped.active · inactive
limitinteger · 1-100

Response fields, each row of data

FieldType
libraryIdstring
adUrlstring
pageUrlstring
advertiserany
isActiveboolean
startDatestring
endDatestring
daysActiveinteger
headlinestring
bodyTextstring
linkDescriptionstring
ctaTextstring
destinationUrlstring
mediaTypestring
mediaUrlstring
formatstring
variantCountinteger
platformslist of string
euReachinteger
reachBreakdownany
cardsany
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · ads
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"ads","subjects":["nike"],"status":"active","limit":25}'

Example response rows

data · made-up names, real field names
[
  {
    "advertiser": "Brewlab Coffee",
    "isActive": true,
    "startDate": "2026-10-01",
    "daysActive": 15,
    "headline": "20% off your first bag",
    "bodyText": "Small-batch beans, roasted every Monday.",
    "ctaText": "Shop now",
    "mediaType": "video",
    "format": "single",
    "variantCount": 2,
    "platforms": [
      "facebook",
      "instagram"
    ],
    "endDate": "2026-10-02",
    "libraryId": "2282493876",
    "adUrl": "https://www.facebook.com/item-1000",
    "pageUrl": "https://www.facebook.com/item-1000",
    "destinationUrl": "https://www.facebook.com/item-1000",
    "mediaUrl": "https://www.facebook.com/item-1000",
    "details": {}
  },
  {
    "advertiser": "Brewlab Coffee",
    "isActive": true,
    "startDate": "2026-09-20",
    "daysActive": 26,
    "headline": "Try the autumn menu",
    "bodyText": "Pumpkin spice, done right.",
    "ctaText": "Get directions",
    "mediaType": "image",
    "format": "single",
    "variantCount": 1,
    "platforms": [
      "facebook"
    ],
    "endDate": "2026-10-06",
    "libraryId": "1516528853",
    "adUrl": "https://www.facebook.com/item-1001",
    "pageUrl": "https://www.facebook.com/item-1001",
    "destinationUrl": "https://www.facebook.com/item-1001",
    "mediaUrl": "https://www.facebook.com/item-1001",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try ads in the playground Examples and pricing for ads
Eventsevents

Events by keyword. Name, date, venue, host, going/interested, tickets.

FieldTypeMeaning
query *string · ≤300 chars
limitinteger · 1-100

Response fields, each row of data

FieldType
eventIdstring
eventUrlstring
eventNamestring
descriptionstring
dateTimestring
startDatestring
durationstring
frequencystring
occurrencesany
categorystring
venueNamestring
venueUrlstring
addressstring
streetstring
citystring
countrystring
latitudenumber
longitudenumber
isOnlineboolean
isPastboolean
isCanceledboolean
hoststring
hostsany
goinginteger
interestedinteger
ticketsany
externalLinkslist of string
coverImageUrlstring
imageCaptionstring
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · events
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"events","query":"jazz festival","limit":20}'

Example response rows

data · made-up names, real field names
[
  {
    "eventName": "Latte Art Night",
    "startDate": "2026-10-24",
    "duration": "3 hours",
    "category": "Food & Drink",
    "venueName": "Brewlab Coffee",
    "city": "Austin",
    "country": "US",
    "isOnline": false,
    "going": 84,
    "interested": 412,
    "eventId": "1614687254",
    "eventUrl": "https://www.facebook.com/latte-art-night-1000",
    "venueUrl": "https://www.facebook.com/latte-art-night-1000",
    "isPast": false,
    "isCanceled": false,
    "coverImageUrl": "https://img.facebook.com/latte-art-night.jpg",
    "details": {}
  },
  {
    "eventName": "Cupping: New Harvest",
    "startDate": "2026-11-07",
    "duration": "2 hours",
    "category": "Food & Drink",
    "venueName": "Brewlab Coffee",
    "city": "Austin",
    "country": "US",
    "isOnline": false,
    "going": 26,
    "interested": 190,
    "eventId": "1747196447",
    "eventUrl": "https://www.facebook.com/cupping-new-harvest-1001",
    "venueUrl": "https://www.facebook.com/cupping-new-harvest-1001",
    "isPast": false,
    "isCanceled": false,
    "coverImageUrl": "https://img.facebook.com/cupping-new-harvest.jpg",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try events in the playground Examples and pricing for events
Marketplacemarketplace

Marketplace listings from a category or search URL. Title, price, condition, location, attributes, photos.

FieldTypeMeaning
subject *string · ≤400 charsA Marketplace category or search URL.
limitinteger · 1-100

Response fields, each row of data

FieldType
listingIdstring
listingUrlstring
listingTitlestring
descriptionstring
pricestring
priceValuenumber
originalPricestring
currencystring
conditionstring
locationstring
citystring
statestring
countrystring
postalCodestring
latitudenumber
longitudenumber
listedAtstring
primaryPhotostring
photosany
videoUrlstring
attributesany
deliveryOptionslist of string
mileagestring
detailsobject

Every field is present on every row: a value the source had nothing for is null, an empty list is []. details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

example request · marketplace
curl -X POST https://apiforagents.dev/v1/facebook \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"marketplace","subject":"https://www.facebook.com/marketplace/nyc/bicycles","limit":20}'

Example response rows

data · made-up names, real field names
[
  {
    "listingTitle": "Road bike, 54 cm, barely used",
    "price": "$420",
    "priceValue": 420,
    "currency": "USD",
    "condition": "Used - like new",
    "city": "Austin",
    "state": "TX",
    "country": "US",
    "listedAt": "2026-10-14",
    "listingId": "770737849",
    "listingUrl": "https://www.facebook.com/road-bike-54-cm-barely-used-1000",
    "videoUrl": "https://www.facebook.com/road-bike-54-cm-barely-used-1000",
    "details": {}
  },
  {
    "listingTitle": "Gravel bike, 56 cm",
    "price": "$650",
    "priceValue": 650,
    "currency": "USD",
    "condition": "Used - good",
    "city": "Austin",
    "state": "TX",
    "country": "US",
    "listedAt": "2026-10-12",
    "listingId": "151623122",
    "listingUrl": "https://www.facebook.com/gravel-bike-56-cm-1001",
    "videoUrl": "https://www.facebook.com/gravel-bike-56-cm-1001",
    "details": {}
  }
]

An example to show the shape. The rows show the most used fields; a live row carries every field in the table above.

Try marketplace in the playground Examples and pricing for marketplace
Historyhistoryfree

Stored follower/likes series of pages already held. Free.

FieldTypeMeaning
subjects *list of string · 1-10 items
metricenumfollowers · likes · talking_about · review_count · recommend_percent
daysinteger · 1-730
Try history in the playground

Guides and ideas.

Use it from your tools.

More in social.

All platforms