Ebay APIs

16 APIs193 Endpoints4 Categories

API Catalog(13 of 16)

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 endpoints

Browse 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 endpoints

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

1 endpoints

Catalog API

Look up and search eBay's product catalog to find exact matches for items sellers want to list. Listing against a catalog product auto-fills titles, descriptions, item specifics, and stock images - reducing listing creation time and ensuring data accuracy across millions of product entries.

2 endpoints

Charity API

The eBay Charity API lets third-party applications search and look up nonprofit organisations registered with eBay for Charity, the donation programme that lets sellers route a percentage of sale proceeds to a vetted charity. Two endpoints cover the full surface - keyword search across all supported organisations on a marketplace, and detail lookup by charity_org_id - returning legal name, EIN/registration number, logo, and mission summary. Applications use it to power charity pickers in listing flows and to verify a charity reference attached to a listing or sale.

2 endpoints

Deal API

The eBay Deal API is a Limited Release member of the eBay Buy API family that exposes promotional deals and time-bound events along with the eligible items inside each. The four-endpoint surface lets approved partners list current deal items, retrieve event metadata, list active events, and fetch the items associated with a given event. It is used by deal aggregators, browser extensions, and AI shopping agents that need authoritative access to eBay's curated deal inventory rather than scraping the public site.

4 endpoints

Item Feed Service

The eBay Item Feed Service lets approved Buy API partners download bulk TSV_GZIP feed files of eBay items by category, marketplace, and date, plus hourly snapshot files of items that have changed within the last hour. Agents and applications can ingest the full eBay catalogue offline rather than scraping listings or paginating through search. Access is gated to Limited Release partners - applications must be approved by eBay business units before this service can be used in production.

4 endpoints

Logistics API

The eBay Logistics API gives approved sellers programmatic access to eBay-negotiated shipping rates and label generation. Sellers request a shipping quote for a package, choose from a list of live carrier rates valid for a specific time window, and create a shipment that produces a downloadable shipping label. The API consolidates the rate-shop, label-buy, and cancel flows into six endpoints scoped to a single shipment lifecycle.

6 endpoints

Negotiation API

The eBay Negotiation API lets sellers proactively send discounted offers to buyers who have shown interest in their listings, such as adding an item to a watchlist. With two endpoints it identifies eligible items and sends a Send Offer to Interested Buyers (SOIB) discount on those listings. Sellers use it to recover stalled watch-list interest and convert it into completed sales without negotiating one-on-one.

2 endpoints

Recommendation API

The eBay Recommendation API gives sellers programmatic recommendations to improve their listings, starting with Promoted Listings ad recommendations. Its single endpoint, POST /find, returns recommended actions for one or more listingIds, telling the seller which listings would benefit from being promoted and the suggested ad-rate strategies. Sellers integrate it with Promoted Listings flows so they only spend ad budget on listings eBay's models predict will respond.

1 endpoints

Sell Compliance API

The eBay Sell Compliance API tells sellers which of their active listings violate, or are at risk of violating, eBay listing policies - restricted-item rules, missing item specifics, image quality, brand-protection flags, regional take-back disclosures, and others. Two endpoints cover the full surface - /listing_violation_summary returns a count of violations grouped by compliance type, and /listing_violation returns the per-listing detail (listingId, violation reason, recommended fix). Sellers wire it into their listing-management tools so they catch and resolve violations before eBay suppresses or removes the listings.

2 endpoints

Sell Feed API

The eBay Sell Feed API is a bulk-processing surface for sellers - upload large input files (orders, inventory, listings) and download large output reports (LMS reports, customer-service metric tasks, fulfillment exports). It supports three modes: ad-hoc tasks (POST /task or /order_task or /inventory_task), recurring schedules tied to a schedule template (POST /schedule), and on-demand customer-service metric tasks (/customer_service_metric_task). Sellers operating thousands of SKUs use it instead of per-row Sell Inventory and Sell Fulfillment calls - one feed replaces a long sequence of API roundtrips.

23 endpoints

Sell Fulfillment API

The eBay Sell Fulfillment API is where sellers complete the post-checkout half of the transaction - read placed orders, create shipping fulfillments with tracking numbers, issue refunds, and manage payment disputes including evidence upload, contest, and accept actions. The 15 endpoints split across two resources: /order for the order lifecycle and /payment_dispute for buyer-initiated disputes. All operations require a User access token in the seller's context.

15 endpoints

Connect Your Agent

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

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