/vestiairecollective/users

POST /api/vestiairecollective/users

Price: 10 credits

Get one Vestiaire Collective member profile by id, profile URL or username: badges, items sold, listed and bought, followers, shipping speed and vacation status

How to use it

Fetch a Vestiaire Collective member profile. Pass the numeric id when you have it, as returned in seller.id by the product endpoints; a username must match exactly.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Vestiaire Collective user id, profile URL or username (examples: "30063183", "https://us.vestiairecollective.com/profile/30063183/", "eve30063183"; minLength: 1)

Response

• @type string (default: "VestiaireUser")
• id string required
• name string nullable
• username string nullable
• url string nullable
• image string nullable
• bio string nullable
• country_code string nullable
• country string nullable
• segment string nullable
• badges array (default: [])
• sold_count integer nullable
• listed_count integer nullable
• bought_count integer nullable
• wished_count integer nullable
• liked_count integer nullable
• follower_count integer nullable
• following_count integer nullable
• community_rank integer nullable
• pass_rate number nullable
• ships_within string nullable
• is_on_vacation boolean nullable
• has_ongoing_or_upcoming_vacation boolean nullable
• vacation_start_at integer nullable
• vacation_end_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 — No Vestiaire Collective member has this id or username 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.