Depop APIdepop.com ↗
Access Depop listings, seller profiles, reviews, similar products, and the full category tree via a structured JSON API with 9 endpoints.
What is the Depop API?
The Depop API covers 9 endpoints for reading product listings, seller data, and platform discovery signals. search_products lets you query Depop's catalog with filters for brand, color, size, sale status, and sort order, returning paginated summaries with pricing, images, and sold status. Other endpoints expose full product detail, seller profiles and reviews, liked items, trending listings, similar products, and the complete category hierarchy.
curl -X GET 'https://api.parse.bot/scraper/8cd92db4-e548-4ff6-96bd-a5c4ff66bb71/search_products?sort=priceAsc&limit=5&query=nike+shoes&on_sale=false' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace depop-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Depop SDK — search products, browse sellers, and explore trending items."""
from parse_apis.depop_api import Depop, Sort, SellerNotFound
client = Depop()
# Search for Nike shoes sorted by price ascending, capped at 5 results.
for product in client.products.search(query="nike shoes", sort=Sort.PRICE_ASC, limit=5):
print(product.slug, product.pricing.currency_name, product.sold)
# Browse trending items on the platform.
trending = client.products.trending(limit=3).first()
if trending:
print(trending.slug, trending.brand_name, trending.status)
# Get full product details by slug.
detail = client.productdetails.get(slug="roman522-cropped-nike-sweater")
print(detail.attributes.product_title, detail.seller_reviews.reviews_rating)
print(detail.seller_activity.items_sold, detail.seller_activity.last_seen)
# Fetch a seller profile and browse their listings and reviews.
seller = client.sellers.get(username="roman522")
print(seller.username, seller.followers, seller.items_sold)
for listing in seller.listings(limit=3):
print(listing.slug, listing.pricing.currency_name)
for review in seller.reviews(limit=3):
print(review.rating, review.text, review.author_username)
# Typed error handling: catch a missing seller gracefully.
try:
client.sellers.get(username="nonexistent_user_xyz_999")
except SellerNotFound as exc:
print(f"Seller not found: {exc.username}")
print("exercised: products.search / products.trending / productdetails.get / sellers.get / seller.listings / seller.reviews")
Search for products on Depop with various filters. Returns paginated results with product summaries including pricing, images, sizes, and status. Use the cursor from the response to paginate through results.
| Param | Type | Description |
|---|---|---|
| sort | string | Sort order. Accepted values: relevance, priceAsc, priceDesc, newlyListed. |
| brand | string | Brand ID or name to filter by. |
| limit | integer | Number of items to return per page. |
| query | string | Search keyword. |
| sizes | string | Comma-separated size IDs to filter by. |
| colors | string | Comma-separated color names to filter by. |
| cursor | string | Pagination cursor from previous response's cursor field. |
| on_sale | boolean | If true, only return discounted items. |
| category | string | Category slug (e.g. 'mens-accessories-belts'). Values from get_category_tree. |
| condition | string | Condition ID to filter by. |
| price_max | number | Maximum price in USD. |
| price_min | number | Minimum price in USD. |
{
"type": "object",
"fields": {
"meta": "object containing total_count, cursor, and has_more for pagination",
"cursor": "string pagination cursor for the next page",
"products": "array of product summaries with id, slug, status, pricing, preview images, sizes, and sold status"
},
"sample": {
"data": {
"meta": {
"cursor": "Mnw1fDE3ODExNjQwMTU.BOOSTED_EXHAUSTED.0",
"has_more": true,
"total_count": 465998
},
"cursor": "Mnw1fDE3ODExNjQwMTU.BOOSTED_EXHAUSTED.0",
"products": [
{
"id": 779580666,
"slug": "chiarau0323-pink-and-white-nike-shoes-733a",
"sold": false,
"sizes": [
{
"id": 11,
"name": "US 9.5"
}
],
"status": "STATUS_ONSALE",
"pricing": {
"is_reduced": false,
"currency_name": "USD",
"original_price": {
"total_price": "15.00"
}
},
"brand_id": 270,
"brand_name": "Nike"
}
]
},
"status": "success"
}
}About the Depop API
Search and Product Data
search_products accepts query, brand, sizes, colors, on_sale, sort, limit, and cursor parameters and returns a meta object with result_count, has_more, and a cursor for pagination alongside an array of product summaries. Each summary includes id, slug, status, pricing (with currency), preview images, sizes, and sold status. For a single item, get_product_detail accepts a product slug or full URL and returns an attributes object covering product_title, brand, condition, colour, age, source, style, group, product_type, and gender, plus a full pricing breakdown with original_price, national_shipping_cost, and discount info.
Seller Data
get_seller_profile returns a seller's id, username, first_name, last_name, bio, followers, following, items_sold, reviews_total, and a last_seen ISO 8601 timestamp. get_seller_listings and get_seller_likes both paginate using a cursor derived from meta.last_offset_id, while get_seller_reviews uses offset-based pagination via next_offset. Each review object in the feedback array includes a 1–5 rating, text, date, transaction_id, a product preview, and author info.
Discovery and Taxonomy
get_trending returns the same paginated product summary shape as search_products but without a query filter, reflecting currently popular items. get_similar_products takes a numeric product_id from any listing response and returns up to 24 comparable products including brand_id, brand_name, slug, pricing, sizes, status, and images. get_category_tree requires no inputs and returns the full category hierarchy — menswear, womenswear, kidswear, and more — with subcategoryFilterDictionary details and attribute_groups keyed by group ID, each containing product_types with attribute_ids and department assignments.
The Depop API is a managed, monitored endpoint for depop.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when depop.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official depop.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Price monitoring: track
original_priceand discount fields across search results for a given brand or keyword over time. - Seller research: aggregate
items_sold,reviews_total,reviews_rating, andaverage_shipping_daysfrom seller profile and listing endpoints. - Resale arbitrage: combine
search_productswithon_saleandpriceAscsort to surface discounted inventory in specific categories. - Recommendation engine: use
get_similar_productsto surface related listings given a product ID from search or seller listing results. - Category mapping: use
get_category_treeto build a complete Depop taxonomy including subcategory IDs and attribute groups for structured classification. - Trend tracking: poll
get_trendingon a schedule to capture shifts in popular items and pricing across the platform. - Competitive analysis: compare active listing counts, review scores, and follower counts across seller profiles in the same niche.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Depop have an official public developer API?+
What does get_product_detail return that search_products does not?+
get_product_detail returns the full attributes object (brand, condition, colour, age, source, style, gender, product_type), a complete pricing breakdown including national_shipping_cost and discount details, per-size quantity and status data, and seller-level signals: seller_reviews (rating and total) and seller_activity (last_seen, items_sold, average_shipping_days). search_products returns a lighter summary focused on pagination, preview images, and basic pricing.How does pagination work across the different endpoints?+
search_products, get_trending, and get_similar_products use a cursor field from meta.cursor to request the next page. get_seller_listings and get_seller_likes use meta.last_offset_id as the cursor value. get_seller_reviews uses integer offset-based pagination via meta.next_offset. Pass the value from each response's meta into the corresponding parameter for the following request.Does the API expose a seller's sold items history or past transaction details?+
get_seller_listings, aggregate stats like items_sold from get_seller_profile, and per-review transaction IDs from get_seller_reviews, but there is no endpoint returning a historical sold-items feed. You can fork the API on Parse and revise it to add that endpoint.Can I filter search results by category or subcategory ID?+
search_products currently accepts brand, sizes, colors, on_sale, sort, query, limit, and cursor — there is no direct category_id filter parameter. get_category_tree returns the full hierarchy with subcategory IDs and attribute group mappings, but applying those as search filters is not currently supported. You can fork the API on Parse and revise it to add category-scoped search.