Ebay APIs

7 APIs90 Endpoints2 Categories

API Catalog

eBay Account API

Jentic publishes the only available OpenAPI specification for eBay Account API, keeping it validated and agent-ready. The Account API lets eBay sellers configure the operational policies that drive every listing - fulfillment policies, payment policies, return policies, and seller-defined custom policies. It also exposes endpoints for opting into and out of programs (such as the eBay Payments program), retrieving sales tax tables and rate tables, checking advertising eligibility, and reading KYC status. Authentication is OAuth 2.0 with the seller-account scope.

36 endpoints

eBay Compliance API

Jentic publishes the only available OpenAPI specification for eBay Compliance API, keeping it validated and agent-ready. The Compliance API surfaces listing violations that put a seller at risk of removal or suppression - missing GTINs, restricted categories, intellectual-property issues, and other policy breaches. Three endpoints expose detailed violations, summary counts grouped by violation type, and a way to suppress a specific violation once the seller has remediated it. The intended workflow is daily polling, fix at scale, and suppress.

3 endpoints

eBay Sell Account API

Jentic publishes the only available OpenAPI specification for eBay Sell Account API, keeping it validated and agent-ready. The Sell Account API is the modern sell- namespace surface for configuring eBay seller policies - fulfillment, payment, return, and seller-defined custom policies - together with program opt-in/opt-out, KYC status, advertising eligibility, and rate tables. It is the canonical surface for any tool that creates or maintains the operational policies underpinning eBay listings. Authentication is OAuth 2.0 with the sell.account scope.

36 endpoints

eBay Sell Analytics API

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.

4 endpoints

eBay Sell Compliance API

Jentic publishes the only available OpenAPI specification for eBay Sell Compliance API, keeping it validated and agent-ready. Sell Compliance is the canonical sell- namespace surface for eBay listing risk - detailed violations, summary counts grouped by compliance type, and a suppression endpoint for clearing remediated violations. Sellers, agencies, and catalogue automation tools rely on it to keep listings free of suppression risk on US, UK, EU, and AU marketplaces. The standard workflow is poll, fix at scale, then suppress.

3 endpoints

eBay Seller Service Metrics API

Jentic publishes the only available OpenAPI specification for eBay Seller Service Metrics API, keeping it validated and agent-ready. This surface exposes the analytics that drive an eBay seller's standing - customer service metrics, the seller standards profile per program and cycle, and a per-listing traffic report covering impressions, clicks, and CTR. It is published under the unbracketed slug and is functionally identical to sell-analytics. Authentication is OAuth 2.0 with the analytics-read scope.

4 endpoints

Seller Service Metrics API

Jentic publishes the only available OpenAPI specification for Seller Service Metrics API, keeping it validated and agent-ready. The eBay Seller Service Metrics API exposes the analytics that drive a seller's performance standing on eBay - customer service metrics, seller standards profile data, and detailed traffic reports for listings. Sellers and agencies use it to monitor late-shipment rates, defect rates, and impressions/clicks per listing. Authentication is OAuth 2.0 with the standard eBay seller scopes.

4 endpoints

Connect Your Agent

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" | sh

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" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.