API reference
Facebook Marketplace Item API
One Marketplace listing in full: description, photos, attributes, availability and price as displayed. Fields the seller did not publish stay null.
Endpoint
GET/v1/facebook/marketplace-itemlive · proven2 creditsParameters
Query parameters
| Name | Required | Description | Example |
|---|---|---|---|
id | yes | Listing id from facebook/marketplace-search (or pass url). | 28157874247229481 |
url | no | Full marketplace item URL — alternative to id. | — |
dry_run | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. | 1 |
Examples
Make the request
curl "https://www.monocrawl.com/v1/facebook/marketplace-item?id=28157874247229481" \ -H "x-api-key: mn_your_key_here"
TypeScript
const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
"https://www.monocrawl.com/v1/facebook/marketplace-item?id=28157874247229481",
{ headers: { "x-api-key": key } },
);
const body = await res.json();
if (!body.success) {
// one error shape for every endpoint — see /docs/errors
throw new Error(`${body.error.type}: ${body.error.message}`);
}
console.log(body.data, "credits left:", body.credits_remaining);Python
import os
import requests
res = requests.get(
"https://www.monocrawl.com/v1/facebook/marketplace-item?id=28157874247229481",
headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
timeout=60,
)
body = res.json()
if not body["success"]:
# one error shape for every endpoint — see /docs/errors
raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")
print(body["data"], "credits left:", body["credits_remaining"])Response
Response fields and example
This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.
{
"success": true,
"platform": "facebook",
"endpoint": "/v1/facebook/marketplace-item",
"data": {
"attributes": [],
"category_id": "example",
"delivery_types": [],
"description": "example",
"id": "example",
"photos": [
"example"
],
"platform": "example",
"price": {
"formatted": "example"
},
"title": "example",
"url": "https://example.com/example"
},
"credits_used": 2,
"credits_remaining": 99,
"request_id": "req_…",
"cached": false
}The example is illustrative and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.
Schema basis: observed response shapes, not an exhaustive field specification. See schema coverage and validation limits.
Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.
| Field inside data | Type | Meaning |
|---|---|---|
attributes | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
category_id | string | null | Optional category id supplied by this operation. Null means unknown. |
delivery_types | array | null | Source array was empty in the reviewed captures; item fields remain unspecified. |
description | string | null | Source description; null or absent means not supplied. |
id | string | null | Source identifier. Preserve the supplied type and exact value. |
photos | array | null | Optional photos supplied by this operation. Null means unknown. |
platform | string | null | Optional platform supplied by this operation. Null means unknown. |
price | object | null | Source price. Currency, taxes and availability depend on the listing. |
price.formatted | string | null | Optional formatted supplied by this operation. Null means unknown. |
title | string | null | Source title when supplied. |
url | string | null | Original source URL when supplied. |
Optional fields reviewed from preserved successful responses. Additive fields and source variations remain allowed; validate the fields your workflow requires.
The example is invented and illustrates types only; zero and empty values are not claims about a real result.
Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference