Ebay APIs
16 APIs193 Endpoints4 Categories
Categories
API Catalog
Account v1 API
The eBay Sell Account API gives sellers programmatic control over their account configuration - eBay business policies (fulfillment, payment, return), custom seller-defined policies, sales-tax tables, opt-in to eBay seller programmes, KYC status, advertising eligibility, and rate-table lookups. Most write endpoints require a User access token issued through the OAuth Authorization Code grant; the API is designed to be the configuration layer that listing flows depend on, so policy IDs returned here are referenced from the Sell Inventory and Sell Marketing APIs.
36 endpointsBrowse API
Jentic publishes the only available OpenAPI specification for the eBay Browse API, keeping it validated and agent-ready. The Browse API is eBay's primary buyer-side discovery surface - search items by keyword, GTIN, image, category, or aspect, retrieve full item detail by item_id, expand item-group variations, and check whether a part fits a given vehicle through the compatibility resource. It also bridges legacy eBay item-IDs from the Finding API to the new RESTful item_id format. Most operations accept an Application access token, so agents can run product discovery without per-user OAuth.
7 endpointsBuy Marketing API
The eBay Buy Marketing API surfaces merchandised eBay products by metric - currently best-selling - so applications can recommend products that are actually moving on eBay rather than guessing from search ranking. Each merchandised product entry includes the listing reference, image, and price snapshot, ready for use in price-comparison sites, deal aggregators, and AI shopping agents. The single GET /merchandised_product endpoint accepts a category_id and metric_name and returns a ranked list, making the API simple to integrate as a discovery layer on top of the larger Browse API.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.