/gumtree/sellers/listings

POST /api/gumtree/sellers/listings

Price: 10 credits

List a Gumtree seller's live ads, addressed by the ID of any of their ads: for each ad returns title, price, location, posting date, promotion flags and images.

How to use it

List a Gumtree seller's live ads by the ID of any ad they posted (Gumtree seller pages are keyed by ad ID, not by user ID). Returns ad cards with id, url, title, price (GBP), description, city/region, posted_at, status, category_id, promotion flags, seller_id, is_pro_seller, attributes and image/images/image_count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ad string required — ID of any ad posted by the seller (or a listing / seller page URL containing it) - Gumtree seller pages are addressed by ad ID (examples: "1800348038", "https://www.gumtree.com/sellerads/1800348038?userId=14514295"; minLength: 1)
• count integer required — Max number of listings to return (min: 1)

Response

• @type string (default: "GumtreeAdCard")
• id string required
• url string required
• price number nullable
• currency string (default: "GBP")
• description string nullable
• city string nullable
• region string nullable
• distance string nullable
• posted_at integer nullable
• status string nullable
• category_id string nullable
• is_featured boolean (default: false)
• is_urgent boolean (default: false)
• is_standout boolean (default: false)
• is_premium boolean (default: false)
• has_video boolean (default: false)
• seller_id string nullable
• is_pro_seller boolean (default: false)
• favourite_count integer nullable
• attributes object (default: {})
  • * string
• image string nullable
• images array (default: [])
• image_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Seller not found (well-formed but nonexistent/removed ad ID) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.