/reverb/items

POST /api/reverb/items

Price: 1 credit

Get Reverb (reverb.com) listing details by ID or URL

How to use it

Get full details of a Reverb music gear listing by listing ID or URL. Returns title, make/model, price, condition, photos, seller, specs, shipping. Supports currency, shipping_region and locale for multi-region pricing.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• currency string — Display currency for prices in the response. (default: "USD"; one of: "USD", "CAD", "EUR", "GBP", "AUD", "JPY", "NZD")
• shipping_region string — Destination shipping region (affects shipping rates and availability). (default: "US_CON"; one of: "XX", "US_CON", "CA", "GB", "AU", "FR", "DE", "JP", "ID", "US_AK", "US_HI", "US_PR", "US_OTHER")
• locale string — Language for localized text in the response. (default: "en"; one of: "en", "fr", "ja", "es", "de", "it")
• item string required — Reverb listing ID or listing URL (examples: "99409675", "https://reverb.com/item/99409675-1962-fender-stratocaster-sonic-blue"; minLength: 1)

Response

• @type string (default: "ReverbItem")
• id string required
• url string nullable
• listing_title string required
• make string nullable
• model string nullable
• finish string nullable
• year string nullable
• description string nullable
• price number nullable
• currency string nullable
• price_display string nullable
• buyer_price number nullable
• listing_currency string nullable
• condition object nullable
  • @type string (default: "ReverbCondition")
  • uuid string nullable
  • name string nullable
  • slug string nullable
• categories array (default: [])
  • @type string (default: "ReverbCategory")
  • uuid string nullable
  • name string nullable
• state string nullable
• is_auction boolean (default: false)
• accepts_offers boolean (default: false)
• offer_count integer (default: 0)
• inventory integer nullable
• shop_id integer nullable
• shop_name string nullable
• shop_alias string nullable
• is_shop_preferred_seller boolean (default: false)
• shop_feedback_count integer nullable
• shop_rating_percentage number nullable
• location object nullable
  • @type string (default: "ReverbLocation")
  • region string nullable
  • locality string nullable
  • country_code string nullable
  • display_location string nullable
• shipping object nullable
  • @type string (default: "ReverbShipping")
  • has_local_pickup boolean (default: false)
  • has_free_expedited boolean (default: false)
  • rates array (default: [])
    • @type string (default: "ReverbShippingRate")
    • region_code string nullable
    • price number nullable
    • currency string nullable
    • display string nullable
    • is_carrier_calculated boolean (default: false)
• images array (default: [])
• videos array (default: [])
• view_count integer nullable
• watch_count integer nullable
• sku string nullable
• is_handmade boolean (default: false)
• is_sold_as_is boolean (default: false)
• origin_country_code string nullable
• comparison_shopping_page_id string nullable
• created_at integer nullable
• published_at integer nullable
• shipping_policy string nullable
• return_policy string nullable
• accepted_payment_methods array (default: [])

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 — Listing 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.