Facebook Marketplace Location Search API

What is the Facebook Marketplace Location Search API?

Resolve a city/place query into Facebook Marketplace location hubs with id (Facebook city_page.id — same value marketplace-search listings expose as cityPageId), slug, city/state, and coordinates when available. marketplace-search already accepts a city string with no lat/lng required — use this endpoint when the name is ambiguous (Austin TX vs Austin MN vs Austin IN) or you need id/coordinates before searching. Bare ambiguous cities (Austin, Portland, Springfield) resolve from a local table in typically under 1s; every other query geocodes globally (typically under 2s) instead of a ~28s Facebook hub scrape. Each row carries idResolved — true when id is present and joinable to listing.cityPageId; false rows are still valid marketplace-search location values via name/slug. Envelope timings{path,hubMs,hubCount,geocodeMs,totalMs} including on 504/404. Flat 2 credits.

What you get

• id = Facebook city_page.id when known (join to search cityPageId)
• idResolved on every row — false rows still work as marketplace-search location via name/slug
• Global geocode for cities outside the US table (İzmir, Şanlıurfa, Chicago, …)

Platform limits

Honest ceilings from the upstream platform surface — not Captapi bugs. Unexpected truncation here is usually the platform, not us.

• Optional geocode — skip when marketplace-search's city string is enough.
• id is omitted (idResolved=false) when Facebook's city_page.id is unknown — pass name or slug to marketplace-search.
• Typical latency under 2s; the old ~28s Facebook hub scrape is no longer the default path.

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

curl "https://api.captapi.com/v1/facebook/marketplace-location-search?q=Austin" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Example response

{
  "success": true,
  "data": {
    "query": "Austin",
    "totalReturned": 3,
    "locations": [
      {
        "id": "109791499039942",
        "cityPageId": "109791499039942",
        "slug": "austin",
        "name": "Austin, TX",
        "city": "Austin",
        "state": "TX",
        "latitude": 30.2677,
        "longitude": -97.7475
      },
      {
        "slug": "austin-minnesota",
        "name": "Austin, MN",
        "city": "Austin",
        "state": "MN",
        "latitude": 43.6666,
        "longitude": -92.9746
      }
    ]
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Parameters

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 2 credits. Pass cache=true for a free 24h cache hit; default is always fresh.

How it works

1. 1. Sign up — get 100 free credits, no card required.
2. 2. Create a key from your dashboard.
3. 3. Send one request to /v1/facebook/marketplace-location-search and parse the JSON response.

Use cases

Frequently asked questions

More Facebook Marketplace APIs