Facebook Marketplace Item API examples for SocQ

Collect public Facebook Marketplace items from listing URLs, returning listing content, seller details, price and location, media, and availability as normalized records.

Try Facebook Marketplace Item API · Get an API key · Documentation · All SocQ examples

Use cases

• Enrich selected search results: Use listing descriptions, seller fields, additional media, attributes, delivery values, and precise location context to expand a chosen set of Marketplace search results.
• Recheck price and availability: Compare normalized price, strikethrough price, availability text, and live, pending, sold, shipping, buy-now, or messaging flags for known listing URLs.
• Compare selected item attributes: Organize titles, categories, condition attributes, locations, delivery types, prices, and media across a defined list of public items.
• Preserve listing snapshots: Store listing identity, source URL, public content, state fields, created_at, and collected_at as a point-in-time record for later comparison.

API behavior

• Submit one or more public Facebook Marketplace URLs whose path begins with /marketplace/item/{numeric_id}.
• Each distinct valid URL can produce at most one listing; unavailable items can return no record without stopping other URLs.
• Seller identity, coordinates, descriptions, media, attributes, delivery values, timestamps, and state flags are optional public fields.
• The endpoint is read-only and does not buy, sell, edit, reserve, ship, or message about an item.

All requests use the shared asynchronous flow:

submit -> task_id -> poll task -> read every cursor page -> save results

Quick start

cp .env.example .env
export SOCQ_API_KEY="your-api-key"

Run the complete Node.js workflow:

cd node
npm start

Run the complete Python workflow:

python3 -m pip install -r python/requirements.txt
python3 python/main.py

Both examples load payload.example.json, retry transient API responses, wait for task completion, read every cursor page, and save an enriched public Marketplace item dataset with seller, price, location, media, and availability details to output/results.json.

Never expose SOCQ_API_KEY in browser code, mobile apps, public repositories, screenshots, fixtures, or logs.

Request

POST https://api.socq.ai/v1/facebook-marketplace/item
Authorization: Bearer <SOCQ_API_KEY>
Content-Type: application/json

{
  "urls": [
    "https://www.facebook.com/marketplace/item/1000000000000000/"
  ]
}

The submit response contains data.task_id. Poll the task endpoint until data.status becomes succeeded or failed, then continue with data.results.next_cursor while data.results.has_more is true.

Complete workflow example

The Node.js and Python programs implement the production-shaped happy path:

1. Load and validate configuration.
2. Submit the endpoint-specific payload.
3. Retry rate-pressure and transient server responses with bounded backoff.
4. Poll the asynchronous task with a ten-minute application timeout.
5. Stop cleanly on a failed task and surface the public error message.
6. Read all cursor pages instead of silently returning only the first page.
7. Write a stable JSON artifact containing task metadata and normalized records.

Use the synthetic files in fixtures/ for tests and documentation. They do not contain customer, account, or production data.

Production notes

See docs/production-notes.md for validation, retry, timeout, pagination, deduplication, logging, and endpoint-specific guidance.

Responsible use and platform scope

• Use only publicly accessible Facebook Marketplace locations, listing search results, item pages, and fields supported by the selected endpoint.
• Do not use the examples to access private seller information, restricted listings, login-only surfaces, or authentication controls.
• SocQ is not an official API of the represented social platform and is not affiliated with or endorsed by that platform.
• Before production use, assess the laws, platform terms, privacy obligations, and retention requirements that apply to your organization and use case.
• Collect only the fields needed for a defined purpose, restrict access, set retention periods, and support correction or deletion workflows where required.
• Platform names and trademarks belong to their respective owners.

This section describes the public-data boundary; it is not legal advice or a guarantee that every use case is permitted in every jurisdiction.

Repository contents

Path	Purpose
curl/request.md	Copy-paste submit, poll, and pagination requests
node/index.mjs	Complete Node.js workflow
python/main.py	Complete Python workflow
payload.example.json	Safe endpoint-specific request body
fixtures/	Synthetic submit and task response shapes
docs/production-notes.md	Production integration guidance