/rebag/products

POST /api/rebag/products

Price: 20 credits

Get one Rebag item by handle, numeric id or URL, in stock or sold: price, condition and condition notes, designer, materials and colours, measurements, included accessories, watch and jewelry specifications, retail and original prices, store location, photos and timestamps.

How to use it

Fetch the full record of an item found through rebag/products/search. Every Rebag listing is a single physical item, so is_available false means it has sold and price is the last asking price.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Rebag product handle, numeric product id or product URL (examples: "handbags-chloe-marcie-shoulder-bag-leather-medium4326642", "9046718480561", "https://shop.rebag.com/products/handbags-chloe-marcie-shoulder-bag-leather-medium4326642"; minLength: 1)

Response

• @type string (default: "RebagProduct")
• id string required
• alias string nullable
• url string nullable
• clean_title string nullable
• brand string nullable
• product_type string nullable
• price number nullable
• currency string nullable
• rplus_price number nullable
• standard_price number nullable
• original_price number nullable
• estimated_retail_price number nullable
• percent_of_retail number nullable
• is_available boolean nullable
• condition string nullable
• condition_details string nullable
• item_number string nullable
• sku string nullable
• barcode string nullable
• upc string nullable
• clair_code string nullable
• brand_code string nullable
• image string nullable
• images array (default: [])
• tags array (default: [])
• collections array (default: [])
• seo_title string nullable
• seo_description string nullable
• exterior_material string nullable
• exterior_color string nullable
• interior_material string nullable
• interior_color string nullable
• hardware_color string nullable
• hermes_color string nullable
• has_strap boolean nullable
• accessories array (default: [])
• size_and_fit array (default: [])
• size_guide_image string nullable
• guide_url string nullable
• store_location string nullable
• serial_number string nullable
• reference_number string nullable
• production_year integer nullable
• has_papers boolean nullable
• has_extra_links boolean nullable
• movement string nullable
• complications string nullable
• case_material string nullable
• bezel_material string nullable
• band_material string nullable
• band_color string nullable
• dial_color string nullable
• dial_material string nullable
• crystal string nullable
• water_resistance string nullable
• collateral array (default: [])
• material string nullable
• non_gem_material string nullable
• metal_type string nullable
• metal_finish string nullable
• total_item_weight string nullable
• signature string nullable
• signature_hallmark_location string nullable
• hallmarks_type string nullable
• gemstones array (default: [])
• new_gemstones array (default: [])
  • @type string (default: "RebagGemstone")
  • stone_count integer nullable
  • total_carat_weight string nullable
  • shape string nullable
  • color string nullable
  • saturation string nullable
  • clarity string nullable
  • transparency string nullable
• pearls array (default: [])
• new_pearls array (default: [])
  • @type string (default: "RebagPearl")
  • size string nullable
  • shape string nullable
  • body_color string nullable
  • overtone string nullable
  • luster string nullable
  • surface string nullable
• favorites_count integer nullable
• views_count integer nullable
• batch_published_at integer nullable
• first_look_ends_at integer nullable
• created_at integer nullable
• updated_at integer nullable
• published_at integer nullable
• description string nullable
• variant_id string nullable
• color string nullable
• inventory_quantity integer nullable
• weight number nullable
• weight_unit string 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 Rebag product has this handle or 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.

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.