ruby-lane.com APIruby-lane.com ↗
Access Ruby Lane listings, item details, shop profiles, and category browsing via API. Extract prices, conditions, descriptions, and seller info.
curl -X GET 'https://api.parse.bot/scraper/4cad73ed-f164-468f-a7ca-9c33ca518e36/search_items' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for vintage and antique items by keyword
| Param | Type | Description |
|---|---|---|
| page | integer | Page number |
| sort | string | Sort order (e.g. price_low_high) |
| queryrequired | string | Search keyword |
{
"type": "object",
"fields": {
"page": "string",
"items": "array",
"query": "string"
},
"sample": {
"page": "1",
"items": [
{
"url": "https://www.rubylane.com/item/...",
"image": "https://cdn.example.com/item.jpg",
"price": "$150.00",
"title": "Vintage Gold Brooch",
"shop_name": "Antique Treasures"
}
],
"query": "jewelry"
}
}About the ruby-lane.com API
The Ruby Lane API provides 4 endpoints for extracting listing data from Ruby Lane, a curated marketplace for antiques, collectibles, and vintage jewelry. The search_items endpoint accepts a keyword query plus optional pagination and sort parameters, returning matched item arrays. get_item_details delivers per-listing fields including price, currency, condition, description, and seller name. browse_category and get_shop round out coverage of category-level and dealer-level data.
Search and Category Browsing
The search_items endpoint accepts a required query string along with an optional page integer and sort parameter (e.g. price_low_high). It returns the matched items array alongside the echoed query and current page string — useful for paginating through result sets programmatically. The browse_category endpoint works similarly but navigates by category slug such as jewelry, dolls, or art, letting you pull all listings within a specific Ruby Lane category without crafting a keyword query.
Item Detail Retrieval
Passing a full item listing URL to get_item_details returns a structured record with six fields: name, price (as a number), currency, condition, description, and seller. The condition and description fields are particularly relevant for antiques and collectibles research, where item provenance and grading directly affect valuation. The numeric price field enables sorting and comparison logic on the client side without string parsing.
Shop Profiles
The get_shop endpoint accepts a shop_slug taken from a Ruby Lane shop URL and returns the shop's shop_name, location, and description. This is the primary way to profile individual dealers — for instance, to identify seller geography or build a directory of shops by region. Shop-level data complements item-level data when building sourcing tools or dealer research workflows.
- Compare prices across Ruby Lane listings for a specific antique or collectible by keyword using
search_items - Monitor new listings in a category like
artordollsby pollingbrowse_categorywith pagination - Extract item condition and description from
get_item_detailsto assess authenticity and grading for resale research - Build a dealer directory using
get_shopto collect shop name, location, and description across multiple sellers - Aggregate currency-normalized pricing data from
get_item_detailsfor market valuation analysis - Track seller inventory by combining
get_shopslug data withsearch_itemsqueries filtered to that seller - Identify regional antique dealers by extracting the
locationfield from multipleget_shopcalls
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Ruby Lane offer an official developer API?+
What does `get_item_details` return, and does it include seller ratings or reviews?+
name, price, currency, condition, description, and seller. Seller ratings and buyer reviews are not currently included in the response. The API covers item-level attributes and seller name. You can fork it on Parse and revise to add a reviews or ratings endpoint.Does the API return sold or historical listings?+
search_items, browse_category, and get_item_details. Sold or archived listings are not currently covered. You can fork the API on Parse and revise it to add an endpoint targeting sold item data if that becomes available from the source.How does pagination work across endpoints?+
search_items and browse_category both accept an optional page integer parameter. The response echoes back the current page as a string. There is no total-page-count field returned, so you would need to iterate pages until an empty items array is returned to detect the end of results.Can I retrieve all items listed in a specific shop?+
get_shop returns the shop's profile fields — shop_name, location, and description — but does not return an inventory list directly. A shop's listings are not currently enumerable through a dedicated shop-inventory endpoint. You can fork the API on Parse and revise it to add shop-level inventory browsing.