/depop/users/likes

POST /api/depop/users/likes

Price: 20 credits

Get the listings a Depop user has liked

How to use it

Get the listings a Depop user has liked, by username, user ID or profile URL, including items that have since sold. Each item carries its seller's user ID.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Depop username, numeric user ID or profile URL (examples: "raddad82", "42869444", "https://www.depop.com/raddad82/"; minLength: 1)
• count integer required — Max number of results to return (examples: 24; min: 1)
• country string — Buyer region the prices are quoted for (default: "us"; one of: "us", "gb", "de", "fr", "it", "ie", "ca", "au", "nz")

Response

• @type string (default: "DepopItemCard")
• id string required
• alias string required
• url string required
• status string nullable
• active_status string nullable
• description string nullable
• brand_id string nullable
• brand_name string nullable
• brand_alias string nullable
• category_id string nullable
• category_name string nullable
• categories array (default: [])
• gender string nullable
• group string nullable
• product_type string nullable
• is_kids boolean (default: false)
• condition string nullable
• colours array (default: [])
• styles array (default: [])
• eras array (default: [])
• sources array (default: [])
• attributes array (default: [])
  • @type string (default: "DepopAttribute")
  • name string required
  • values array (default: [])
• price number nullable
• original_price number nullable
• discounted_price number nullable
• strikethrough_price number nullable
• currency string nullable
• is_reduced boolean (default: false)
• discount_percentage number nullable
• like_count integer nullable
• listed_quantity integer nullable
• sizes array (default: [])
  • @type string (default: "DepopSize")
  • id string required
  • name string nullable
  • quantity integer nullable
  • status string nullable
• size_set_id string nullable
• location string nullable
• country string nullable
• shipping_provider string nullable
• parcel_size string nullable
• shipping_payer string nullable
• is_boosted boolean (default: false)
• boosted_at integer nullable
• seller_id string nullable
• repop_original_item_id string nullable
• repop_original_seller_id string nullable
• image string nullable
• images array (default: [])
• created_at integer nullable
• updated_at 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 — User not found 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.