eBay Sell Analytics API
Browse all Ebay APIsAgent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligenceoauth24 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read eBay seller performance signals - customer service metrics, seller standards profile, and listing traffic - to forecast standing and find underperforming listings.
Use for: I want to forecast my eBay seller standing for next month, Get impressions and clicks per listing in the last 7 days, Retrieve the customer service metric for ITEM_NOT_AS_DESCRIBED, Check whether the seller is at risk of dropping below standard
Not supported: Does not handle order management, listing creation, or financial settlement - use for reading eBay seller analytics and traffic data only.
Jentic publishes the only available OpenAPI specification for eBay Sell Analytics API, keeping it validated and agent-ready. Sell Analytics is the canonical sell- namespace surface for eBay seller performance data - customer service metrics, seller standards profile, and the traffic report covering impressions, clicks, and click-through rate per listing. Sellers, agencies, and listing-optimisation tools rely on it to forecast standing, target underperforming listings, and detect early signals of metric decline. Authentication is OAuth 2.0 with the analytics-read scope.
Install Jentic One Beta
Connect the eBay Sell Analytics API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the eBay 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%2Fapi.ebay.com%2Febay-sell-analytics-api" | 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%2Fapi.ebay.com%2Febay-sell-analytics-api" | 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 eBay Sell Analytics API.
Pull a customer service metric by metric type and evaluation type for peer or seller comparison
List every seller standards profile across programs and CURRENT/PROJECTED cycles
Retrieve a specific seller standards profile by program and cycle for status forecasting
Generate a traffic report covering impressions, clicks, and CTR per listing
Filter analytics by date range, marketplace, and dimension to slice by region or category
Use Cases
Patterns agents use eBay Sell Analytics API for, with concrete tasks.
★ Standing forecast and early-warning
Operations teams managing high-volume eBay accounts can poll GET /seller_standards_profile daily and compare CURRENT to PROJECTED cycles. When the projected status drops below ABOVE_STANDARD the team can react before the cycle closes. This keeps Top Rated discounts and search visibility intact.
Call GET /seller_standards_profile, compare CURRENT and PROJECTED for each program, and alert when PROJECTED drops below ABOVE_STANDARD
Listing optimisation pipeline
Listing optimisation tools can call GET /traffic_report to identify low-CTR listings and feed them into image, title, and price test queues. The traffic_report endpoint supports dimension and metric query parameters so the response can be grouped by listing or category and filtered by marketplace.
Call GET /traffic_report grouped by listing for the last 30 days and return the 20 listings with the lowest CTR for optimisation
Customer-service metric benchmarking
Customer-service teams can fetch GET /customer_service_metric/{customer_service_metric_type}/{evaluation_type} with PEER_BENCHMARK to see how the seller compares to peers in the same category. The breakdown highlights which categories drag the metric, so investment lands where it most reduces defect rate.
Call GET /customer_service_metric/ITEM_NOT_AS_DESCRIBED/PEER_BENCHMARK and surface categories where the seller exceeds the peer rate
Agent-driven daily health digest via Jentic
An AI agent acting as a virtual eBay account manager can search Jentic for the eBay seller-standards operation, run it daily, and produce a one-paragraph digest highlighting the changes worth a human reviewing. Jentic stores the OAuth credentials so the agent never sees raw tokens.
Search Jentic for 'check ebay seller standing', execute GET /seller_standards_profile across active programs, and emit a daily summary
Key Endpoints
4 endpoints — jentic publishes the only available openapi specification for ebay sell analytics api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/customer_service_metric/{customer_service_metric_type}/{evaluation_type}
Retrieve a customer service metric
GET
/seller_standards_profile
List seller standards profiles
GET
/seller_standards_profile/{program}/{cycle}
Get a profile by program and cycle
GET
/traffic_report
Pull listing impressions, clicks, and CTR
GET
/customer_service_metric/{customer_service_metric_type}/{evaluation_type}
Retrieve a customer service metric
GET
/seller_standards_profile
List seller standards profiles
GET
/seller_standards_profile/{program}/{cycle}
Get a profile by program and cycle
GET
/traffic_report
Pull listing impressions, clicks, and CTR
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the eBay Sell Analytics API by hand means running its OAuth2 flow and coding your own reads of the customer service metric and traffic report endpoints. Through Jentic you install once, import the eBay Sell Analytics API from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the metric type and evaluation type in the URL path (/customer_service_metric/{customer_service_metric_type}/{evaluation_type}), and every operation here is read-only, so a rule can pin your agent to reading a single metric type. You choose the operations it may call, so any beyond those you name are not included.
Credential isolation
Your eBay token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read seller analytics' or 'pull the traffic report', and Jentic returns the matching eBay Sell Analytics 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.
Alternative
eBay Seller Service Metrics API (legacy slug)
Identical surface published under the original hyphen-bracketed slug
Avoid for new work; only used where existing imports require the bracketed slug
FAQs
Specific to using eBay Sell Analytics API through Jentic.
Why is there no official OpenAPI spec for eBay Sell Analytics API?
eBay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call eBay Sell Analytics API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Sell Analytics API use?
OAuth 2.0 with the analytics-read scope (https://api.ebay.com/oauth/api_scope/sell.analytics.readonly), obtained via eBay's user-token flow. Through Jentic, the OAuth credentials live in your Jentic One instance and access tokens are minted per call.
How is sell-analytics related to the seller-service-metrics-api slugs?
All three slugs (sell-analytics, seller-service-metrics-api, and the legacy hyphen-bracketed variant) share the same 4 endpoints. Sell Analytics is the modern slug under eBay's sell- namespace and is preferred for new integrations.
Can I retrieve a traffic report for a specific marketplace through Jentic?
Yes. Install with `pip install jentic`, search for `pull ebay listing traffic report`, load the schema for GET /traffic_report, populate marketplace_ids and the date range, and execute. The response includes impressions, clicks, and CTR aggregated per the requested dimension.
What are the rate limits for the Sell Analytics API?
Sell Analytics inherits eBay's standard daily call ceiling - typically 5,000 calls per day per application key in production, with per-second burst caps. Check your eBay Developer Program dashboard for the exact ceiling on your keyset.
What is the difference between CURRENT and PROJECTED cycles on the seller standards profile?
CURRENT returns the seller's status for the closed evaluation period. PROJECTED returns the rolling forecast that determines next period's status - use this to detect risk before the cycle closes.
Can I limit what my agent is allowed to do with the eBay Sell Analytics API?
Yes. Jentic One is self-hosted, so you run it and your own rules decide which of the four read-only operations your agent may call and which credentials it may use. Because this API is read-only and puts the metric type and evaluation type directly in the URL path, such as /customer_service_metric/{customer_service_metric_type}/{evaluation_type}, you can pin the agent to a single metric or evaluation type and expose only the traffic report or seller standards profile reads you approve. Any operation you do not explicitly name stays out of the agent's reach.
GET STARTED