/poshmark/users

POST /api/poshmark/users

Price: 1 credit

Get a Poshmark seller (closet) profile by username or closet URL

How to use it

Get a Poshmark seller's public closet profile by username or closet URL. Choose the marketplace region (poshmark.com US / poshmark.ca CA). Returns display name, handle, bio, location, avatar and cover images, follower/following/listing/share counts, seller rating and 5-star counts, order count and items-sold.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• domain string — Poshmark marketplace region to query (default: "poshmark.com"; one of: "poshmark.com", "poshmark.ca")
• user string required — Poshmark username or closet URL (examples: "lauramiranda857", "https://poshmark.com/closet/lauramiranda857"; minLength: 1)

Response

• @type string (default: "PoshmarkUser")
• id string required
• alias string nullable
• display_handle string nullable
• full_name string nullable
• first_name string nullable
• last_name string nullable
• gender string nullable
• bio string nullable
• city string nullable
• state string nullable
• website_url string nullable
• college_year string nullable
• home_domain string nullable
• status string nullable
• image string nullable
• cover string nullable
• follower_count integer (default: 0)
• following_count integer (default: 0)
• brands_following_count integer (default: 0)
• listing_count integer (default: 0)
• share_count integer (default: 0)
• seller_rating_count integer (default: 0)
• seller_rating_value integer (default: 0)
• seller_5_star_rating_count integer (default: 0)
• seller_order_count integer (default: 0)
• items_sold_display string nullable
• created_at integer nullable
• last_active_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.