eBay Seller Leads API avatar

eBay Seller Leads API

Pricing

from $0.45 / result

Go to Apify Store
eBay Seller Leads API

eBay Seller Leads API

eBay seller lookup for one /usr/, /str/ or feedback URL across eight marketplaces, returning a 40-field seller record with membership, Top Rated status, 1/6/12-month feedback counts, four detailed ratings with the number of ratings behind each, Store categories, sales and followers.

Pricing

from $0.45 / result

Rating

0.0

(0)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

1

Bookmarked

3

Total users

0

Monthly active users

5 hours ago

Last modified

Share

eBay Seller Leads API is an ebay seller lookup that turns one public seller, Store or feedback URL into one 40-field record covering identity, reputation over three time windows, membership, detailed ratings and Store signals.

eBay's seller-ratings guide explains that feedback percentage, feedback score, items sold and detailed seller ratings help readers assess a seller; this Actor places those public signals in a structured Dataset row.

Apify Users Apify Runs $0.015 per profile 8 marketplaces API + MCP ready

  • Three URL forms, one entity. Start with /usr/, /str/ or /fdbk/feedback_profile/; Store slugs are resolved to seller usernames before the record is assembled.
  • Forty stable top-level fields. Identity and marketplace keys lead, public feedback and Store facts follow, and processor plus processed_at close every row.
  • Eight marketplace domains. The input contract accepts the United States, United Kingdom, Germany, France, Italy, Spain, Canada and Australia.
  • Public-page lookup without an eBay developer key. The Actor reads the seller's public feedback and Store surfaces; it does not call the authenticated Browse API.

One successful seller lookup costs one Actor Start plus one Result — $0.025 on the FREE tier.

Why Choose eBay Seller Leads API

This Actor is for a known seller URL when the next step is structured reputation or Store research, not product discovery.

Feedback and Store identity stay separate. username, profile_url and feedback_url identify the seller, while store_slug, store_name and store_url describe the optional Store. That distinction matters because a Store slug often differs from its seller username.

Public reputation remains source-shaped. The row carries positive_percent, feedback_total, positive, neutral and negative counts over 1, 6 and 12 months, Top Rated status, four detailed seller ratings and the number of ratings behind each. Missing ratings remain null instead of being estimated.

Store context is included when available. A readable Store contributes its name, description, logo, banner, categories, rounded items-sold count, follower count and brand-Store signal. Sellers without a Store can still return their feedback record.

The lookup stays bounded. One input produces at most one Dataset item. That makes cost, orchestration and downstream joins predictable.

Quick Start Guide

Use the prefilled public Store for a one-result test.

Step 1: Configure

Open the Actor input and enter one URL in seller_url. The Anker scenario uses https://www.ebay.com/str/ankerdirect.

Step 2: Run

Click Start. A Store input is resolved to the underlying seller, then the public feedback page and Store page are read as independent work units.

Step 3: Collect

Open the default Dataset after SUCCEEDED. Confirm there is one row, then review username, positive_percent, feedback_total, detailed ratings and any Store fields your workflow needs.

Input Parameters

One required string controls the whole lookup.

ParameterTypeRequiredDescriptionExample
seller_urlstringYesOne eBay seller profile, Store or feedback URL on a supported marketplace.https://www.ebay.com/str/ankerdirect
{
"seller_url": "https://www.ebay.com/str/ankerdirect"
}

Accepted hosts are ebay.com, ebay.co.uk, ebay.de, ebay.fr, ebay.it, ebay.es, ebay.ca and ebay.com.au, including ordinary subdomains. Listing, search and lookalike-domain URLs are rejected before retrieval.

Output Data Schema

One successful lookup writes one row with these 40 top-level fields.

GroupFields
Identityplatform, username, profile_url, feedback_url
Marketplace and membershipmarketplace, marketplace_country, member_since, member_country
Reputation (12 months)is_top_rated, positive_percent, feedback_total, positive_count, neutral_count, negative_count
Recent reputationpositive_count_6m, neutral_count_6m, negative_count_6m, positive_count_1m, neutral_count_1m, negative_count_1m
Detailed seller ratingsdsr_description, dsr_shipping, dsr_delivery, dsr_communication
Ratings behind each scoredsr_description_count, dsr_shipping_count, dsr_delivery_count, dsr_communication_count
Storestore_url, store_slug, store_name, store_description, logo_url, banner_url, categories, items_sold, followers, is_brand_store
Provenanceprocessor, processed_at

An abbreviated row from the shared Anker scenario looks like this:

{
"platform": "eBay",
"username": "ankerdirect",
"profile_url": "https://www.ebay.com/usr/ankerdirect",
"marketplace": "ebay.com",
"member_since": "2010-03-04",
"is_top_rated": true,
"positive_percent": 99.8,
"feedback_total": 312836,
"positive_count": 30331,
"neutral_count": 72,
"negative_count": 47,
"positive_count_6m": 13262,
"positive_count_1m": 1981,
"dsr_description": 4.9,
"dsr_description_count": 3889,
"dsr_shipping": 5.0,
"dsr_shipping_count": 6951,
"dsr_delivery": 5.0,
"dsr_communication": 5.0,
"store_name": "Anker Official Store",
"items_sold": 1000000,
"followers": 34000,
"is_brand_store": true
}

Counts and ratings can change whenever eBay updates the source. The complete row preserves all 40 keys; nullable source values remain null and Store categories remain an array.

Integration Examples

The same one-field input works through REST, Apify clients, Make.com, n8n and the hosted Apify MCP server.

Actor ID

The current API Actor ID is:

kPSPzx8UOL1KYVcn6

The name form agentx/ebay-seller-leads-api resolves to the same Actor.

HTTP

curl -X POST 'https://api.apify.com/v2/acts/kPSPzx8UOL1KYVcn6/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"seller_url":"https://www.ebay.com/str/ankerdirect"}'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("kPSPzx8UOL1KYVcn6").call(
run_input={"seller_url": "https://www.ebay.com/str/ankerdirect"}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items

JavaScript

const { ApifyClient } = require('apify-client');
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('kPSPzx8UOL1KYVcn6').call({
seller_url: 'https://www.ebay.com/str/ankerdirect',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Make.com and n8n

In Make.com, use Run an Actor with Actor ID kPSPzx8UOL1KYVcn6 and map seller_url. In n8n, POST the same JSON to https://api.apify.com/v2/acts/kPSPzx8UOL1KYVcn6/runs, wait for SUCCEEDED, then read the returned defaultDatasetId.

MCP

Connect an MCP client to https://mcp.apify.com, call agentx/ebay-seller-leads-api, and pass seller_url with the Anker Store URL. See Apify's MCP documentation for current OAuth and Bearer-token setup.

Pricing

On the FREE tier, one seller Result costs $0.01500, Actor Start costs $0.01000, and the smallest successful run totals $0.02500.

TierActor StartSeller ResultOne-result total
FREE$0.01000$0.01500$0.02500
BRONZE$0.01000$0.01350$0.02350
SILVER$0.01000$0.01200$0.02200
GOLD$0.01000$0.01125$0.02125
PLATINUM$0.01000$0.01125$0.02125
DIAMOND$0.01000$0.01125$0.02125

Actor Start is one event per gigabyte of run memory with a one-event minimum. Result is charged only when the one seller row is written; there is no separate per-field, Store-page or feedback-page event. Check live pricing before budgeting because prices can change.

Use Cases

Use the Actor where a known eBay seller needs a repeatable public-data profile.

  • Seller due diligence. Review feedback percentage, the 1-, 6- and 12-month positive, neutral and negative counts, membership date and detailed ratings before a human makes a sourcing decision. The short windows separate a seller trading now from one whose volume is older.
  • Store lead enrichment. Add Store name, description, categories, items sold and followers to an existing lead identified by URL.
  • Marketplace comparison. Run known sellers across the eight supported domains and compare normalized reputation and Store fields while retaining the marketplace source.
  • Reputation monitoring. Schedule the same seller URL, keep timestamped rows and compare feedback totals, percentage and detailed ratings over time.
  • Store classification. Use is_brand_store, categories and branding assets to organize a reviewed Store directory without treating the flag as legal brand verification.

Alternatives

Choose the route that matches the starting entity and required authorization.

  • Manual eBay review is appropriate for an occasional visual check but does not create a stable Dataset row or scheduled history.
  • eBay Browse API searches listings by keyword, category or product and requires an Application access token; choose it for authenticated listing discovery, not this one-seller profile contract.
  • An eBay listing scraper starts from products or searches and produces listing rows rather than one consolidated seller and Store record.
  • A custom collector gives full control but adds parser maintenance, proxy operations, schema design and monitoring work.

Limits and Troubleshooting

The Actor reads changing public pages, so unavailable source fields and temporary access failures must remain visible to downstream workflows.

  • At most one row per run. Invalid, missing or unreadable sellers produce zero Dataset rows rather than a fabricated profile.
  • Store data is optional. A real seller without a public Store can return reputation fields with null Store values and an empty categories array.
  • Low-history sellers can lack ratings. Feedback percentage and detailed ratings may be null when eBay does not publish enough history; each rating count is null with them, and a low count qualifies an otherwise high score.
  • Store slug and username can differ. Use the returned username and store_slug instead of assuming the input path is both.
  • Counts are source observations. items_sold and followers can be rounded by eBay; do not reconstruct precision the source did not publish.

For a reproducible valid URL that fails, open an Issue with the run ID, sanitized URL, expected behavior, actual behavior and a short log excerpt. Never include an API token.

Trust and Reliability

The public contract is one required input, 40 ordered Dataset fields, eight accepted marketplace domains and two registered charged events.

Input validation rejects unsupported hosts before retrieval. The output keeps eBay facts distinct from processor provenance and does not add lead scores, contact guesses or seller-quality labels. The eBay feedback-profile guide confirms that overall score, positive percentage, detailed ratings and registration date are public profile concepts.

Treat every row as a time-stamped source observation. Retain the run ID and input URL when a business decision needs traceability, and recheck the live eBay page for consequential use.

Use public seller information for legitimate purposes and comply with eBay's current terms, Apify policies, applicable laws, privacy rules and communication restrictions.

Do not use the Actor to bypass marketplace protections, misrepresent a seller, infer protected traits or automate consequential decisions without review. Minimize retained personal data, control Dataset access and define a deletion schedule appropriate to the purpose.

eBay Seller Leads API is independent and is not affiliated with, endorsed by or operated by eBay.

Frequently Asked Questions

The answers describe the one-seller runtime contract and its public data boundaries.

Is this an ebay seller leads api for one known URL?

Yes. Submit one supported seller, Store or feedback URL and receive at most one 40-field seller record.

Can this Actor find ebay sellers by product keyword?

No. It begins with a known seller URL. Use a listing-search product when the starting point is a product keyword and seller discovery is the goal.

Which eBay URL forms are accepted?

The input accepts /usr/, /str/ and /fdbk/feedback_profile/ paths on eight supported marketplace domains.

Does a successful run always include Store details?

No. Seller reputation can be available when the seller has no Store or the Store page is unavailable; Store fields then remain null or empty.

Are feedback and detailed ratings guaranteed?

No. eBay may withhold percentage or detailed ratings for low-history sellers, and the Actor preserves that absence.

Is Top Rated status a guarantee of seller quality?

No. It is an eBay-published status observed at processing time, not an independent certification or a substitute for due diligence.

Can I submit several seller URLs in one run?

No. The schema accepts one seller_url; orchestrate separate calls for a list and retain each Dataset ID.

AgentX publishes 77 Actors — the three closest e-commerce and business surfaces come first, followed by the complete catalog.

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask product questions in the AgentX community, or report reproducible bugs through the Actor's Issues tab.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 12, 2026