canonical: https://jentic.com/apis/ebay.com/sell-analytics # Ebay Sell Analytics API 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. ## For AI agents Read eBay seller-performance data - traffic reports, customer-service metrics with peer benchmarks, and seller-standards profile ratings. Four user-context endpoints. ## Scope Does not handle order data, listing creation, or financial reporting - use for seller-performance metrics (traffic, defect rates, standards) only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **traffic_report** — Listing-level impression, click, and conversion metrics filterable by date, marketplace, and dimension - **customer_service_metric** — Customer-service ratings (case rates, defect rates) with peer-group benchmark - **seller_standards_profile** — Seller-standards status (Top Rated, Above Standard, Below Standard) per programme and cycle ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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 - **eBay Sell Account API** — Sell Account configures the seller; Sell Analytics measures how that configuration is performing. - **eBay Sell Fulfillment API** — Fulfillment metrics drive customer-service rates; Sell Analytics surfaces the resulting score. - **eBay Browse API** — Browse exposes the buyer-side view of listings whose traffic Sell Analytics measures. ## FAQ ### 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.