Ebay Sell Analytics API
Browse all Ebay APIs65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyAnalyticsBusiness Intelligenceoauth24 EndpointsREST
For Agents
Read eBay seller-performance data - traffic reports, customer-service metrics with peer benchmarks, and seller-standards profile ratings. Four user-context endpoints.
Use for: Get the traffic report for the seller's listings on EBAY_US for the last 30 days, Retrieve the customer-service metric for shipment_non_delivery_rate, List all seller standards profiles for the seller's current programmes, Compare this cycle's defect rate against the previous cycle
Not supported: Does not handle order data, listing creation, or financial reporting - use for seller-performance metrics (traffic, defect rates, standards) only.
The eBay Sell Analytics API returns three kinds of seller-performance data - listing traffic reports, customer-service metrics benchmarked against a peer group, and seller-standards profile ratings (Top Rated, Above Standard, etc.). Sellers and the multi-channel tools they use call it to identify which listings are losing impressions, which customer-service measures are dragging the seller status down, and where the seller sits relative to peers. All four endpoints require a User access token in the seller's context.
Install Jentic One Beta
Connect the Sell Analytics API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sell Analytics API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Febay.com%2Fsell-analytics" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Febay.com%2Fsell-analytics" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Sell Analytics API.
Pull a traffic report showing impressions, click-through rate, and sales conversion per listing
Read customer-service metric ratings benchmarked against a peer group of comparable sellers
Retrieve the seller-standards profile (Top Rated / Above Standard / Below Standard) for a programme and cycle
Compare current-cycle metrics with the previous evaluation cycle to spot regressions
Filter traffic reports by date range, marketplace, and listing dimension for a focused dashboard
Use Cases
Patterns agents use Sell Analytics API for, with concrete tasks.
★ Performance dashboard in a multi-channel SaaS
Multi-channel seller tools build a unified performance dashboard by calling /traffic_report for impressions and conversion, /customer_service_metric/{type}/{evaluation_type} for shipping, returns, and case rates, and /seller_standards_profile for the headline status badge. The dashboard refreshes daily and surfaces which listings are losing visibility before the seller's status itself slips.
Call /traffic_report for last 30 days on EBAY_US, /customer_service_metric/SHIPMENT_NON_DELIVERY_RATE/CURRENT, and /seller_standards_profile, then render them in a single dashboard
Defect-rate alerting before status downgrade
When a seller approaches the Above Standard threshold for a customer-service metric, the integration reads /customer_service_metric/{type}/PROJECTED and compares it with the seller's peer-group benchmark in the same response. An alert fires when the projected rate exceeds the benchmark by more than the cycle's tolerance, giving the seller time to act before the next evaluation.
Call /customer_service_metric/ITEM_NOT_RECEIVED_RATE/PROJECTED and alert if the rate is above the peerBenchmark.metricValue
Listing-level traffic regression analysis
/traffic_report supports dimension filtering by listingId, so analysts can identify the small set of listings driving most of a marketplace's impression drop. The integration pulls the report at listing granularity for two adjacent date ranges and surfaces the SKUs that lost the most impressions, which feeds back into a Sell Inventory API update job.
Pull /traffic_report by LISTING for the last 30 days and the prior 30, diff impressions per listingId, return the bottom 10
AI agent integration via Jentic
An AI agent that helps a seller diagnose a sales drop searches Jentic for 'eBay seller traffic report'. Jentic returns /traffic_report with its required parameters (dimension, metric, filter). The agent loads the schema, executes the call with a User access token issued through Jentic's vault, and presents the result alongside seller-standards context fetched from /seller_standards_profile.
Use Jentic to search 'eBay seller traffic report', load /traffic_report, and execute it with dimension=LISTING and date range last 30 days
Key Endpoints
4 endpoints — the ebay sell analytics api returns three kinds of seller-performance data - listing traffic reports, customer-service metrics benchmarked against a peer group, and seller-standards profile ratings (top rated, above standard, etc.
METHOD
PATH
DESCRIPTION
GET
/traffic_report
Get listing-level traffic and conversion metrics
GET
/customer_service_metric/{customer_service_metric_type}/{evaluation_type}
Get a customer-service metric with peer benchmark
GET
/seller_standards_profile
List all seller-standards profiles for the seller
GET
/seller_standards_profile/{program}/{cycle}
Get a seller-standards profile for a specific programme and cycle
GET
/traffic_report
Get listing-level traffic and conversion metrics
GET
/customer_service_metric/{customer_service_metric_type}/{evaluation_type}
Get a customer-service metric with peer benchmark
GET
/seller_standards_profile
List all seller-standards profiles for the seller
GET
/seller_standards_profile/{program}/{cycle}
Get a seller-standards profile for a specific programme and cycle
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Analytics API
- AI-Aware (B)65/100
67
Foundational Compliance69
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability90
Security56
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
67
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
88%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
90
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
90%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
56
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
56%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the eBay Sell Analytics API by hand means implementing eBay's OAuth 2.0 authorization-code flow for a seller user token, refreshing it, and pointing requests at the api.ebay.com sell/analytics host. Through Jentic you install once, import the Sell Analytics API from the API Directory, store the eBay OAuth credentials once, and your agent calls it.
Permission scoping
Some operations put the resource id in the URL path, such as /customer_service_metric/{customer_service_metric_type}/{evaluation_type} and /seller_standards_profile/{program}/{cycle}, so a rule can pin your agent to one metric type or standards cycle. Every endpoint here is read-only, so the agent reports traffic and performance metrics and nothing more.
Credential isolation
Your eBay OAuth seller credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get an eBay seller traffic report' or 'check eBay seller standards', and Jentic returns the matching /traffic_report or /customer_service_metric operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Sell Analytics API through Jentic.
What authentication does the Sell Analytics API use?
The Sell Analytics API uses OAuth 2.0 with the Authorization Code grant - all four endpoints operate in the authenticated seller's context, so a User access token is required. Through Jentic, the seller's refresh token lives in your Jentic One instance and the agent receives only a scoped access token for the sell.analytics scope.
Can I get listing-level traffic metrics with the Sell Analytics API?
Yes. /traffic_report accepts a dimension parameter that includes LISTING, so you can pull impressions, click-through rate, and sales conversion per listingId. Filter by date range and marketplace to narrow the result set, then aggregate client-side as needed.
What are the rate limits for the Sell Analytics API?
Sell Analytics falls under the Sell APIs user-context daily quota issued per application-and-user pair. Call /user_rate_limit on the Developer Analytics API and inspect the sell.analytics entry to see the current seller's remaining call count and reset window.
How do I retrieve the seller-standards profile through Jentic?
Search Jentic for 'get eBay seller standards profile', load GET /seller_standards_profile (or /seller_standards_profile/{program}/{cycle} for a specific programme), and execute it with the seller's User access token. Install with pip install jentic. Get started with Jentic One, the self-hosted execution layer.
What customer-service metrics are supported by the API?
Supported customer_service_metric_type values include ITEM_NOT_RECEIVED_RATE, RETURN_RATE, CLAIMS_AND_DISPUTES_RATE, SHIPMENT_NON_DELIVERY_RATE, and TRACKING_UPLOAD_RATE among others. The evaluation_type can be CURRENT (the active evaluation cycle) or PROJECTED (the projected end-of-cycle value).
Does the response include peer-group benchmarks?
Yes. Each customer-service metric response includes a peerBenchmark block with the comparable seller group's metric value, so you can render 'your rate vs. peer rate' without an extra call. The peer group is selected by eBay based on category, sales volume, and marketplace.
Can I limit what my agent is allowed to do with the eBay Sell Analytics API?
Yes. Because Jentic One is self-hosted, you write the rules that decide which of the four read-only operations your agent may call and which eBay seller credentials it may use. Several operations carry the resource id in the URL path, such as /customer_service_metric/{customer_service_metric_type}/{evaluation_type} and /seller_standards_profile/{program}/{cycle}, so a rule can pin the agent to a single metric type or standards cycle. Every endpoint here is read-only, so the agent can report traffic, customer-service metrics, and seller-standards data and nothing more.
GET STARTED