POST /api/ssense/products
Price: 5 credits
Get one SSENSE product by id or URL: designer, category, description, composition, price in the chosen country's currency, sale status, per-size stock with measurements, model fit and photos
Fetch the full SSENSE product for one id, as returned in id by the SSENSE product search. The country sets the price and currency.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)product string required — SSENSE product id or product page URL (examples: "19523371", "https://www.ssense.com/en-us/men/product/rick-owens/black-tower-wide-bela-trousers/19523371"; minLength: 1)country string — Storefront country; it sets the assortment, the prices and the currency (default: "us"; one of: "ad", "ae", "af", "ag", "ai", "al", "am", "ao", "aq", "ar", "as", "at", "au", "aw", "az", "ba", "bb", "bd", "be", "bf", "bg", "bh", "bi", "bj", "bm", "bn", "bo", "br", "bs", "bt", "bv", "bw", "by", "bz", "ca", "cc", "cd", "cf", "cg", "ch", "ci", "ck", "cl", "cm", "cn", "co", "cr", "cv", "cw", "cx", "cy", "cz", "de", "dj", "dk", "dm", "do", "dz", "ec", "ee", "eg", "eh", "er", "es", "et", "fi", "fj", "fk", "fm", "fo", "fr", "ga", "gb", "gd", "ge", "gf", "gh", "gi", "gl", "gm", "gn", "gp", "gq", "gr", "gs", "gt", "gu", "gw", "gy", "hk", "hm", "hn", "hr", "ht", "hu", "id", "ie", "il", "in", "io", "iq", "is", "it", "jm", "jo", "jp", "ke", "kg", "kh", "ki", "km", "kn", "kr", "kw", "ky", "kz", "la", "lb", "lc", "li", "lk", "lr", "ls", "lt", "lu", "lv", "ly", "ma", "mc", "md", "me", "mg", "mh", "mk", "ml", "mm", "mn", "mo", "mp", "mq", "mr", "ms", "mt", "mu", "mv", "mw", "mx", "my", "mz", "na", "nc", "ne", "nf", "ng", "ni", "nl", "no", "np", "nr", "nu", "nz", "om", "pa", "pe", "pf", "pg", "ph", "pk", "pl", "pm", "pn", "pr", "ps", "pt", "pw", "py", "qa", "re", "ro", "rs", "ru", "rw", "sa", "sb", "sc", "se", "sg", "sh", "si", "sj", "sk", "sl", "sm", "sn", "so", "sr", "st", "sv", "sx", "sz", "tc", "td", "tf", "tg", "th", "tj", "tk", "tm", "tn", "to", "tr", "tt", "tv", "tw", "tz", "ua", "ug", "um", "us", "uy", "uz", "va", "vc", "ve", "vg", "vi", "vn", "vu", "wf", "ws", "ye", "yt", "za", "zm", "zw")@type string (default: "SsenseProduct")id string requiredurl string nullablealias string nullablename string nullabledescription string nullablecomposition string nullablestyle_code string nullabledepartment string nullablecountry string nullablebrand object nullable@type string (default: "SsenseBrand")id string nullablename string nullablealias string nullablecategory object nullable@type string (default: "SsenseCategoryRef")id string requiredalias string nullablelevel integer nullablecategory_path array (default: [])@type string (default: "SsenseCategoryRef")id string requiredalias string nullablelevel integer nullableprice number nullableregular_price number nullablecurrency string nullableis_on_sale boolean nullableis_final_sale boolean nullableis_in_stock boolean nullablecountry_of_origin string nullableimages array (default: [])sizes array (default: [])@type string (default: "SsenseSize")id string nullablename string nullableconversion string nullablesize_system string nullabledisplay_order integer nullablesku string nullablegtin string nullablestock_count integer nullablemeasurements array (default: [])@type string (default: "SsenseMeasurement")name string requiredcm number nullableinch number nullablemodel object nullable@type string (default: "SsenseModelInfo")size_worn string nullablemeasurements array (default: [])@type string (default: "SsenseMeasurement")name string requiredcm number nullableinch number nullableis_displayed boolean nullablecreated_at integer nullable422 — 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 SSENSE product has this 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.