What you get#
Onekey exposes eBay as 2 endpoints behind one API key: 1 endpoint return one record (data is an object) and 1 endpoint return a list (data is an array). Every answer uses the same envelope (success, data, metadata, error), the cost is reported in metadata.credits_charged, and fields are mapped onto the unified schema so the code you write for eBay also works for the rest of the e-commerce & marketplaces category.
Endpoints#
| Endpoint | What it does | Parameters | Credits | Status |
|---|---|---|---|---|
item | One eBay item by Browse item id. | item_id* | 1 | beta |
search | Search eBay listings (Browse API). | q* | 5 | beta |
A * marks a required parameter. Each endpoint name links to its reference page with the full parameter table, caching window and a recorded response.
Make a request#
This calls ebay.item (1 credit, beta). Replace YOUR_API_KEY with your key; sign up, no card. 1,000 free credits cover the open-platform endpoints. Hard-to-reach platforms (X, TikTok, Instagram, Reddit, and others marked on their page) need a verified email and a purchased pack.
curl "https://api.onekey.dev/v1/ebay/item?item_id=v1%7C110123456789%7C0" \
-H "x-api-key: YOUR_API_KEY"Fields you get back#
These unified fields come back from eBay, with the same names as on every other platform. The count is how many of its 2 mapped endpoints return the field; a field the source lacks is null, never missing. 1 platform-specific field (ext.<name>) come on top, documented on each endpoint page.
| Field | Type | Endpoints |
|---|---|---|
content.id | string | 2 |
entity.name | string | 2 |
entity.url | URL | 2 |
listing.condition | string | 2 |
listing.currency | string | 2 |
listing.price | number | 2 |
listing.seller | string | 2 |
media.thumbnailUrl | URL | 2 |
content.createdAt | ISO 8601 date | 1 |
entity.category | string | 1 |
entity.description | string | 1 |
listing.brand | string | 1 |
The full schema is in Unified schema.
Pricing#
eBay calls cost 1 to 5 credits, flat per endpoint. Free when served from cache (0.2 credit for a cached response over 100 KB). Invalid, failed or not-found calls are not charged. See pricing for credit packs.