# eBay Product Details Scraper (`alpha-scraper/ebay-product-details-scraper`) Actor Extract structured product data from eBay listings with the eBay Product Details Scraper. Collect product titles, prices, images, seller details, conditions, shipping, returns, descriptions, item specifics, and item numbers from one or more eBay product URLs. - **URL**: https://apify.com/alpha-scraper/ebay-product-details-scraper.md - **Developed by:** [Alpha Scraper](https://apify.com/alpha-scraper) (community) - **Categories:** Videos, Social media, Other - **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.50 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ### eBay Product Details Scraper The **eBay Product Details Scraper** extracts structured product and seller information from one or more eBay product URLs. It is designed for users who need product-level data such as the listing title, price, condition, images, shipping information, delivery details, return policy, seller information, item number, description, and item specifics. The Actor accepts a list of eBay product URLs through the `startUrls` input. Each supported listing is processed and returned as a structured dataset record, making the collected information easier to review, analyze, and use in automated data workflows. This Actor can be useful for product research, marketplace analysis, competitive research, catalog building, listing analysis, and other workflows that require structured eBay product data. ### What Is an eBay Product Details Scraper? An **eBay Product Details Scraper** is a data extraction tool focused on individual eBay product listings. Instead of manually opening listings and copying information field by field, you provide the product URLs and receive structured records containing the information available from those listings. The Actor focuses on product-page details rather than broad search-result collection. For each successfully processed URL, it extracts information from the listing page and, when available, the listing description content. The resulting records are useful when you need consistent product-level information across multiple eBay listings. ### Key Features | Feature | Description | User Benefit | | ----------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------- | | Multiple eBay product URLs | Accepts one or more product URLs through `startUrls` | Collect information from multiple listings in one run | | Product title extraction | Captures the listing's product title | Supports cataloging and product research | | Product price extraction | Extracts the displayed primary price when available | Helps organize listing price data | | Product condition | Collects the listing condition text | Useful for product comparison and analysis | | Product images | Returns available listing image URLs | Supports image-based catalog and research workflows | | Seller information | Extracts seller name and seller-related information when available | Adds seller context to product records | | Shipping and delivery details | Captures shipping and delivery information exposed on the listing | Useful for marketplace analysis | | Return policy | Extracts available return-policy information | Helps organize listing terms | | Item number | Captures the eBay item identifier when available | Useful for listing identification | | Description extraction | Returns cleaned text from the product description when available | Makes listing content easier to analyze | | HTML description | Preserves cleaned description HTML when available | Useful when formatting or HTML content matters | | Item specifics | Builds a structured key-value collection of listing specifics | Makes product attributes easier to analyze | | Structured dataset output | Pushes successful records as dataset items | Simplifies downstream data processing | ### What Data Can You Extract? The Actor returns a product record containing several categories of eBay listing information. **Product information** includes the product title, price, condition, item number, product images, and listing URL. **Seller information** can include the seller name, the number of items sold when available, and positive feedback information exposed by the listing. **Fulfillment information** includes shipping information, delivery information, and return-policy details when those values are present on the page. **Description content** is returned in two forms. `item_description` contains cleaned text, while `item_description_html` contains cleaned HTML where the listing description is available. **Item specifics** are returned as a structured object containing attribute names and their corresponding values, such as product characteristics displayed in the listing's item-specifics section. Because the Actor reads information available on individual listings, the exact availability of some fields can vary from product to product. ### Why Use This Actor? Manual collection from eBay product pages can become repetitive when a workflow requires information from many listings. This Actor provides a structured way to process multiple product URLs and collect the information into dataset records. A consistent output structure can make it easier to compare listings, create internal product datasets, prepare research data, or feed marketplace information into later processing steps. The Actor is particularly useful when your workflow already has a known set of eBay product URLs and you need information from the individual listing pages rather than general search results. ### Benefits The eBay Product Details Scraper provides several practical benefits for product-data workflows: - **Automation:** Reduces repetitive manual copying from individual eBay listings. - **Structured results:** Returns standardized fields for easier processing and analysis. - **Multiple-input processing:** Lets you provide more than one product URL in a single run. - **Product research support:** Brings listing information together in a consistent dataset. - **Seller context:** Includes seller-related fields alongside product information. - **Description analysis:** Provides both text and HTML versions of the listing description when available. - **Attribute organization:** Stores item specifics as key-value data rather than leaving them only as unstructured page content. ### How to Use the eBay Product Details Scraper Using the Actor is straightforward: 1. Open the Actor and provide one or more supported eBay product URLs in `startUrls`. 2. Review the input structure before starting the run. 3. Start the Actor. 4. The Actor processes each provided URL. 5. Successful listings are pushed as structured dataset records. 6. Review the resulting records and use the collected data in your research or automation workflow. For the first run, using a small number of URLs is a practical way to confirm that the listings and output fields match your requirements. ### Input The Actor uses a single input field named `startUrls`. It expects an array of request-style URL objects. Each object should contain a `url` pointing to an eBay product listing. #### Input Fields | Field | Type | Required | Default | Description | | ----------- | ----- | -------- | ------- | ----------------------------------------------- | | `startUrls` | Array | No | `[]` | One or more eBay product URL objects to process | Each URL should point to an eBay product/listing page, such as an `https://www.ebay.com/itm/...` URL. The field is optional. When no usable URLs are provided, the Actor logs that there are no URLs to process and stops without producing product records. ### Input Example ```json { "startUrls": [ { "url": "https://www.ebay.com/itm/205684444053" }, { "url": "https://www.ebay.com/itm/257198772991" } ] } ``` The URL objects can contain full eBay listing URLs, including normal listing URL parameters when they are part of the provided link. ### Output For each successfully processed listing, the Actor creates one structured dataset item. The output contains product, seller, fulfillment, description, item-specific, and identification fields. Some values may be empty when the corresponding information is not available on a particular listing. #### Output Fields | Field | Description | | ----------------------- | ----------------------------------------------------------------- | | `seller_name` | Seller name extracted from the listing | | `seller_items_sold` | Seller item-sales information when available | | `positive_feedback` | Positive feedback information shown for the seller when available | | `product_title` | Product/listing title | | `product_image` | Array of available product image URLs | | `product_price` | Primary product price shown on the listing | | `product_condition` | Product condition text | | `shipping_info` | Shipping information shown on the product page | | `delivery_info` | Delivery information shown on the listing | | `return_policy` | Return-policy information | | `item_number` | eBay item number when available | | `item_description` | Cleaned text version of the product description | | `item_description_html` | Cleaned HTML version of the product description | | `item_specifics` | Structured object containing item-specific labels and values | | `detail_url` | Original product URL processed by the Actor | `product_image` is an array, allowing multiple image URLs to be returned for a listing. `item_specifics` is an object whose keys represent listing attributes and whose values contain the associated attribute values. ### Output Example ```json { "seller_name": "Example Seller", "seller_items_sold": "1,250", "positive_feedback": "99.8%", "product_title": "Example Product Title", "product_image": [ "https://i.ebayimg.com/images/g/example/s-l1600.jpg", "https://i.ebayimg.com/images/g/example2/s-l1600.jpg" ], "product_price": "$49.99", "product_condition": "New", "shipping_info": "Free shipping", "delivery_info": "Estimated delivery", "return_policy": "30 day returns", "item_number": "205684444053", "item_description": "Example product description text.", "item_description_html": "
Example product description text.
", "item_specifics": { "Brand": "Example Brand", "Type": "Example Type" }, "detail_url": "https://www.ebay.com/itm/205684444053" } ``` The values above are illustrative examples. Actual values depend on the specific eBay listing being processed. ### Use Cases The Actor can support several product-data workflows where individual eBay listings are the source of information. **Marketplace research:** Collect listing-level information for product research and marketplace analysis. **Competitive product research:** Compare product titles, prices, conditions, seller information, shipping terms, and other listing attributes. **Catalog building:** Build structured product datasets containing titles, images, prices, descriptions, identifiers, and item specifics. **Product attribute analysis:** Use `item_specifics` to organize structured listing characteristics for analysis or classification. **Seller research:** Combine product information with seller name, sales information, and feedback data when available. **Description research:** Collect listing descriptions for content analysis, categorization, or internal research. **Business intelligence:** Consolidate marketplace listing information into structured records that can be analyzed alongside other business data. ### Advantages The Actor is designed around a simple product-URL-to-dataset workflow. Its structured output makes important listing fields easier to work with than manually copied page content. It also separates description text, description HTML, images, seller information, and item specifics into dedicated fields. The use of a single `startUrls` array keeps the input model simple when your workflow starts with a list of known product URLs. ### Limitations The Actor is intended for individual eBay product URLs rather than general eBay keyword-search scraping. Field availability can vary between listings. For example, seller information, shipping text, delivery information, return-policy text, descriptions, or item specifics may not always be present in the same form on every page. Only successfully processed listings are pushed to the dataset. A URL that returns an unsuccessful response or encounters an error during processing may not produce an output record. The Actor does not expose additional configurable input fields for selecting individual output fields or customizing extraction rules. ### Pros and Cons | Pros | Cons | | ----------------------------------- | ------------------------------------------------------------------ | | Simple URL-based input | Focused on product/listing URLs rather than general search results | | Supports multiple URLs per run | Some fields may vary by listing | | Structured dataset output | Unsuccessful requests may produce no record | | Includes seller and product context | No user-configurable field-selection options | | Returns description text and HTML | Description availability may differ between listings | | Provides structured item specifics | Item-specific attributes depend on the listing | ### Comparison With Alternative Approaches | Capability | This Actor | Manual / Typical Alternative | | -------------------------- | ------------------------------- | --------------------------------------------- | | Multiple product URLs | Supported | Often requires visiting listings individually | | Structured product records | Supported | Usually requires manual formatting | | Product images | Returned as URLs when available | Often copied manually | | Seller information | Included when available | Requires separate manual collection | | Product description text | Returned when available | Requires manual copying | | Description HTML | Returned when available | May require additional page handling | | Item specifics | Returned as a structured object | Often requires manual organization | | Dataset-oriented workflow | Supported through Actor output | Usually requires separate data preparation | This comparison describes workflow characteristics rather than performance claims about other tools or services. ### Competitive Advantages A user may choose this Actor when the starting point is a collection of eBay product URLs and the desired result is a structured listing dataset. Its output combines several useful categories in one record: product information, images, seller information, shipping and delivery details, returns, description content, item specifics, and the original detail URL. The separate text and HTML description fields can also be useful when different downstream workflows need different representations of the same listing content. ### Best Practices Start with a small number of eBay product URLs and review the resulting records before processing a larger collection. Use complete, valid eBay product listing URLs in `startUrls`. Check the `detail_url` field in the results when validating which source page produced each record. For analytical workflows, treat empty fields as potentially unavailable listing data rather than automatically assuming that the source listing has no value for that attribute. Review `item_specifics` across several listings before building a fixed attribute model, because different products may expose different sets of listing attributes. When description content is important, check both `item_description` and `item_description_html` to determine which representation better suits the next stage of your workflow. ### Troubleshooting **Invalid input:** Verify that `startUrls` is an array and that each entry contains a `url` property with a valid eBay product URL. **No results:** Confirm that at least one usable product URL was supplied. Also verify that the URLs point to actual product/listing pages. **Partial results:** Individual listings can differ in the information they expose, and a URL that is not successfully processed will not necessarily create a dataset record. **Missing fields:** Review the original listing and compare it with the corresponding output record. Some seller, shipping, delivery, returns, description, or item-specific information may not be available consistently across listings. **Description missing:** The description fields are populated when the listing's description content is available to the Actor. A listing without accessible description content may return empty description fields. **Temporary failure:** Check the affected URL, confirm that it is still a valid eBay product listing, and retry the run or the affected input when appropriate. ### Frequently Asked Questions #### What does the eBay Product Details Scraper do? The eBay Product Details Scraper collects structured information from eBay product listing URLs, including product, seller, pricing, condition, images, shipping, delivery, returns, descriptions, item specifics, and the item number when available. #### What input does the Actor accept? The Actor accepts an optional `startUrls` array containing one or more objects with a `url` property. The URLs should point to eBay product listings. #### Can I process multiple eBay products in one run? Yes. `startUrls` is an array, so you can provide multiple eBay product URLs for processing in the same run. #### What output does the eBay Product Details Scraper return? Each successfully processed listing is returned as a structured dataset item with fields such as `product_title`, `product_price`, `product_condition`, `product_image`, `seller_name`, `item_number`, `item_description`, `item_description_html`, and `item_specifics`. #### Does the Actor extract product images? Yes. The `product_image` field returns an array of available product image URLs detected from the listing. #### Does it collect seller information? Yes. Seller-related fields include `seller_name`, `seller_items_sold`, and `positive_feedback` when the corresponding information is available on the listing. #### Does the Actor extract product descriptions? Yes. When available, the Actor provides the description as cleaned text in `item_description` and cleaned HTML in `item_description_html`. #### What are item specifics? `item_specifics` is a structured object containing attribute labels and their values from the eBay listing. The exact attributes depend on the individual product page. #### Can the results be used for product research? Yes. The structured listing records can be used for marketplace research, catalog creation, competitive analysis, seller research, and other workflows that require product-level eBay data. #### What should I do when a field is empty? Check the original listing to see whether the information is displayed there. Field availability can vary between eBay product pages, so an empty field does not necessarily indicate a problem with the entire record. ### NLP Keywords - eBay product details scraper - eBay product data extraction - eBay listing scraper - eBay product information - eBay product data - eBay listing details - eBay seller information - eBay product price - eBay product condition - eBay product images - eBay item specifics - eBay item number - eBay listing description - eBay shipping information - eBay delivery information - eBay return policy - structured eBay data - eBay marketplace data - product listing data extraction - eBay product research ### Related Keywords - scrape eBay product page - eBay listing data extractor - extract eBay product information - eBay product URL scraper - eBay item data scraper - eBay listing details extractor - eBay marketplace scraper - eBay product metadata scraper - eBay seller data extraction - eBay product catalog data - eBay listing price extractor - eBay product image extractor - eBay item specifics extractor - eBay description scraper - eBay shipping data extractor - eBay return information scraper - eBay product research tool - structured eBay listing data - eBay product dataset - individual eBay listing scraper ### Final Overview The **eBay Product Details Scraper** provides a straightforward way to turn one or more eBay product URLs into structured listing records. It focuses on individual product pages and collects important information across product, seller, fulfillment, description, and item-specific categories. The workflow is simple: provide valid eBay product URLs through `startUrls`, run the Actor, and review the resulting dataset records. The output is suitable for product research, marketplace analysis, catalog preparation, seller research, and other structured data workflows where listing-level information is required. Because the information available on eBay listings can vary, users should review the returned fields and validate important data before using it in decisions or downstream processes. Contact me: # Actor input Schema ## `startUrls` (type: `array`): List of one or more ebay product URLs (e.g. https://www.ebay.com/...). ## Actor input object example ```json { "startUrls": [ { "url": "https://www.ebay.com/itm/205684444053" }, { "url": "https://www.ebay.com/itm/257198772991?_trkparms=itmf%3D1%26aid%3D1110013%26rkt%3D12%26mech%3D1%26algv%3DSimRXIVICPCWithNsOptCPCRecall%26pmt%3D1%26amclksrc%3DITM%26sd%3D205684444053%26sid%3DAQALAAAAEE9IeqsjsK7PkQiF7xAy2Jk%3D%26itm%3D257198772991%26noa%3D0%26plcampt%3D0%3A13425855013%2C5%3AAG7556853553%26algo%3DHOMESPLICE.SIMRXI%26brand%3DNike%26asc%3D20250821123744%26ao%3D1%26rk%3D4%26pid%3D101196%26b%3D1%26mehot%3Dnone%26lsid%3D0%26meid%3D9dc56c91bb6a47108efa2d3c47ffaa5e%26pg%3D2332490&_trksid=p2332490.c101196.m2219&itmprp=cksum%3A2571987729919dc56c91bb6a47108efa2d3c47ffaa5e%7Cenc%3AAQALAAABAHPwWUUtvvw6diB9oliItpbURBl1%252FA%252Bqr1Qb0AmMMvayNFu0wWNXwElIHQ51VyO%252FEdQp3ArwvqsvFdetDA0W05sxnPjbGgsHvqEAacv8i0bz3JsesfPFFpbQMDivtY%252BTjWNLLM%252BzhlrzHP8t4%252FpwZ85SZAjn%252BqxsvO4kvU4waL9sqYo6mveUpDnGP1o9BMflD1LtO8GX%252BWOA%252FYEwYg3u8m1X4ExkUOXVvyiq4Lp%252FKq30Nr0fbCGbcrXunZEnzzH6HoAF0qMmf2vsXtkp2%252Be91slusVrGSxz9S1%252BbiMpbkEByUdcLxXF84Fwg9drwysO9E76uLV07gFK2FlSGF7cetfQ%253D%7Campid%3APL_CLK%7Cclp%3A2332490&itmmeta=01KN7PYQ2WAV4Y6C8JGM05EAB7" } ] } ``` # Actor output Schema ## `dataset` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://www.ebay.com/itm/205684444053" }, { "url": "https://www.ebay.com/itm/257198772991?_trkparms=itmf%3D1%26aid%3D1110013%26rkt%3D12%26mech%3D1%26algv%3DSimRXIVICPCWithNsOptCPCRecall%26pmt%3D1%26amclksrc%3DITM%26sd%3D205684444053%26sid%3DAQALAAAAEE9IeqsjsK7PkQiF7xAy2Jk%3D%26itm%3D257198772991%26noa%3D0%26plcampt%3D0%3A13425855013%2C5%3AAG7556853553%26algo%3DHOMESPLICE.SIMRXI%26brand%3DNike%26asc%3D20250821123744%26ao%3D1%26rk%3D4%26pid%3D101196%26b%3D1%26mehot%3Dnone%26lsid%3D0%26meid%3D9dc56c91bb6a47108efa2d3c47ffaa5e%26pg%3D2332490&_trksid=p2332490.c101196.m2219&itmprp=cksum%3A2571987729919dc56c91bb6a47108efa2d3c47ffaa5e%7Cenc%3AAQALAAABAHPwWUUtvvw6diB9oliItpbURBl1%252FA%252Bqr1Qb0AmMMvayNFu0wWNXwElIHQ51VyO%252FEdQp3ArwvqsvFdetDA0W05sxnPjbGgsHvqEAacv8i0bz3JsesfPFFpbQMDivtY%252BTjWNLLM%252BzhlrzHP8t4%252FpwZ85SZAjn%252BqxsvO4kvU4waL9sqYo6mveUpDnGP1o9BMflD1LtO8GX%252BWOA%252FYEwYg3u8m1X4ExkUOXVvyiq4Lp%252FKq30Nr0fbCGbcrXunZEnzzH6HoAF0qMmf2vsXtkp2%252Be91slusVrGSxz9S1%252BbiMpbkEByUdcLxXF84Fwg9drwysO9E76uLV07gFK2FlSGF7cetfQ%253D%7Campid%3APL_CLK%7Cclp%3A2332490&itmmeta=01KN7PYQ2WAV4Y6C8JGM05EAB7" } ] }; // Run the Actor and wait for it to finish const run = await client.actor("alpha-scraper/ebay-product-details-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [ { "url": "https://www.ebay.com/itm/205684444053" }, { "url": "https://www.ebay.com/itm/257198772991?_trkparms=itmf%3D1%26aid%3D1110013%26rkt%3D12%26mech%3D1%26algv%3DSimRXIVICPCWithNsOptCPCRecall%26pmt%3D1%26amclksrc%3DITM%26sd%3D205684444053%26sid%3DAQALAAAAEE9IeqsjsK7PkQiF7xAy2Jk%3D%26itm%3D257198772991%26noa%3D0%26plcampt%3D0%3A13425855013%2C5%3AAG7556853553%26algo%3DHOMESPLICE.SIMRXI%26brand%3DNike%26asc%3D20250821123744%26ao%3D1%26rk%3D4%26pid%3D101196%26b%3D1%26mehot%3Dnone%26lsid%3D0%26meid%3D9dc56c91bb6a47108efa2d3c47ffaa5e%26pg%3D2332490&_trksid=p2332490.c101196.m2219&itmprp=cksum%3A2571987729919dc56c91bb6a47108efa2d3c47ffaa5e%7Cenc%3AAQALAAABAHPwWUUtvvw6diB9oliItpbURBl1%252FA%252Bqr1Qb0AmMMvayNFu0wWNXwElIHQ51VyO%252FEdQp3ArwvqsvFdetDA0W05sxnPjbGgsHvqEAacv8i0bz3JsesfPFFpbQMDivtY%252BTjWNLLM%252BzhlrzHP8t4%252FpwZ85SZAjn%252BqxsvO4kvU4waL9sqYo6mveUpDnGP1o9BMflD1LtO8GX%252BWOA%252FYEwYg3u8m1X4ExkUOXVvyiq4Lp%252FKq30Nr0fbCGbcrXunZEnzzH6HoAF0qMmf2vsXtkp2%252Be91slusVrGSxz9S1%252BbiMpbkEByUdcLxXF84Fwg9drwysO9E76uLV07gFK2FlSGF7cetfQ%253D%7Campid%3APL_CLK%7Cclp%3A2332490&itmmeta=01KN7PYQ2WAV4Y6C8JGM05EAB7" }, ] } # Run the Actor and wait for it to finish run = client.actor("alpha-scraper/ebay-product-details-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://www.ebay.com/itm/205684444053" }, { "url": "https://www.ebay.com/itm/257198772991?_trkparms=itmf%3D1%26aid%3D1110013%26rkt%3D12%26mech%3D1%26algv%3DSimRXIVICPCWithNsOptCPCRecall%26pmt%3D1%26amclksrc%3DITM%26sd%3D205684444053%26sid%3DAQALAAAAEE9IeqsjsK7PkQiF7xAy2Jk%3D%26itm%3D257198772991%26noa%3D0%26plcampt%3D0%3A13425855013%2C5%3AAG7556853553%26algo%3DHOMESPLICE.SIMRXI%26brand%3DNike%26asc%3D20250821123744%26ao%3D1%26rk%3D4%26pid%3D101196%26b%3D1%26mehot%3Dnone%26lsid%3D0%26meid%3D9dc56c91bb6a47108efa2d3c47ffaa5e%26pg%3D2332490&_trksid=p2332490.c101196.m2219&itmprp=cksum%3A2571987729919dc56c91bb6a47108efa2d3c47ffaa5e%7Cenc%3AAQALAAABAHPwWUUtvvw6diB9oliItpbURBl1%252FA%252Bqr1Qb0AmMMvayNFu0wWNXwElIHQ51VyO%252FEdQp3ArwvqsvFdetDA0W05sxnPjbGgsHvqEAacv8i0bz3JsesfPFFpbQMDivtY%252BTjWNLLM%252BzhlrzHP8t4%252FpwZ85SZAjn%252BqxsvO4kvU4waL9sqYo6mveUpDnGP1o9BMflD1LtO8GX%252BWOA%252FYEwYg3u8m1X4ExkUOXVvyiq4Lp%252FKq30Nr0fbCGbcrXunZEnzzH6HoAF0qMmf2vsXtkp2%252Be91slusVrGSxz9S1%252BbiMpbkEByUdcLxXF84Fwg9drwysO9E76uLV07gFK2FlSGF7cetfQ%253D%7Campid%3APL_CLK%7Cclp%3A2332490&itmmeta=01KN7PYQ2WAV4Y6C8JGM05EAB7" } ] }' | apify call alpha-scraper/ebay-product-details-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,alpha-scraper/ebay-product-details-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/yO14zJl13DOctTxis/builds/gIsx64eVtO0nuFrNE/openapi.json