Fetch full eBay listing records for many item IDs in one call, with unresolved IDs reported in not_found and billing counted per ID.

View all eBay Product Listings & Seller Data endpoints →

Looks up several eBay listings at once by item number and returns, for each one, the same full record as the single-item detail operation. Send item_ids as a comma-separated string of the digits that follow /itm/ in a listing URL, and optionally choose domain (13 verified sites such as com, co.uk, de, com.au and ca) to set the marketplace and currency. The operation overview states up to 40 IDs per request, while the item_ids parameter note says up to 15 per call, so chunk at 15 if you want to stay inside the stricter figure. The response uses an ok/meta/data envelope. data.items[] holds item_id, title, url, price{value,currency,raw}, list_price, condition, availability, brand, model, mpn, images[], category_path, item_specifics{}, seller{name,feedback_pct,feedback_count}, shipping{rate,currency,country}, return_policy{days,method}, best_offer, end_time, watchers, quantity_available and quantity_sold, plus auction fields such as bids and current_bid on auction listings. data.not_found[] lists IDs that were ended, removed or invalid instead of dropping them silently, and meta.requested and meta.upstream_calls report how many IDs were sent and billed. Billing is per item ID, not per request: eBay has no batched item endpoint, so N IDs cost the same as N single lookups, and the saving is wall-clock time (the operation notes measure 25.6 s sequential versus 4.1 s for 8 IDs). Observed in a live probe (item_ids 287070621317,301782776848, domain com): HTTP 200 with ok true, meta.requested 2, meta.upstream_calls 2, two active InStock records, an empty not_found and data.unavailable null. In that probe the first record had null seller.feedback_pct, seller.feedback_count, category_path and return_policy, so treat those fields as optional, while the second record returned return_policy {days 30, method ReturnByMail} and a three-level category path. The 40-ID ceiling, the auction fields and a non-empty not_found array come from the operation notes and documented example, not from the probe.

API Features

Many item IDs in one request Pass a comma-separated item_ids string and get one record per resolved listing in data.items[]. The overview says up to 40 IDs per request and the parameter note says 15, so size chunks to the stricter figure.
Same full record as item detail Each entry carries title, price, list_price, condition, brand, model, MPN, images, category path, item specifics, seller reputation, shipping terms, return policy and quantity fields, not just a search card.
Explicit not_found list IDs that eBay does not resolve, such as ended, removed or invalid listings, come back in data.not_found[] instead of vanishing, so a batch can never hide which item went missing.
Billing counter in meta meta.requested, meta.upstream_calls and billing_note state how many IDs were sent and billed, so you can budget each batch and stop a job once a spend cap is reached.
Concurrent fetching for lower latency Listings are fetched in parallel (meta.concurrency was 8 in the probe). The operation notes measure 25.6 s sequential versus 4.1 s for 8 IDs, so you save wall-clock time but not billed lookups.
Thirteen verified marketplace sites domain selects com, co.uk, de, com.au, ca, fr, it, es, nl, at, ch, ie or pl and sets currency and local listings; other eBay country sites such as com.sg and com.hk are also accepted.

Live API Demo

POST /api/project/ebay/items-batch

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X POST 'https://api.opendata-api.com/api/project/ebay/items-batch?key=<API_KEY>' \ -H 'Content-Type: application/json' \ -d '{"item_ids":"<item_ids>"}'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

How many item IDs can I send in one call?

The operation overview says up to 40 IDs per request, but the item_ids parameter note says up to 15 per call, and the live probe used 2. To stay inside the stricter documented figure, send chunks of 15 or fewer, and compare meta.requested with the number of IDs you sent.

Am I billed per request or per item ID?

Per item ID. eBay has no batched item endpoint, so each ID is its own lookup and is priced like a single item-detail call. meta.upstream_calls is documented as equal to the number of IDs you sent and meta.billing_note reads "priced per item ID, not per call"; in the probe, 2 IDs gave requested 2 and upstream_calls 2. Batching saves time, not billed lookups.

What happens to item IDs that eBay does not resolve?

They are returned in data.not_found[] rather than dropped, so you can compare the IDs you sent with the IDs returned. Ended, removed or invalid numbers are the documented causes. The probe returned an empty not_found; a non-empty array is shown only in the documented example response. Because meta.upstream_calls equals the number of IDs sent, unresolved IDs are still counted in it.

Is a batch faster than calling item-detail repeatedly?

Yes in wall-clock terms, because the lookups run concurrently. The operation notes measure 25.6 s sequential versus 4.1 s for 8 IDs (6.2x). The 2-ID probe reported meta.latency_ms of about 3,800 with meta.concurrency 8. The number of billed lookups is the same either way.

Is there a cheaper way if I only need price, title and condition?

The operation notes describe the search operation with query (id1,id2,id3), eBay's own OR syntax, as a single billed lookup that returns card-level fields only (item_id, title, price, condition, shipping, image, url). It was measured at about 6 IDs per call, with a seventh dropped, and it returns no item specifics, seller or return policy. These figures come from the notes, not from the probe.

What format should item_ids use?

Use a comma-separated string of eBay item numbers, the digits after /itm/ in a listing URL, for example 287070621317,301782776848. The parameter note also says a list is accepted. This operation does not take listing URLs; use the item-detail operation when you only have a pasted link.

Why are some seller or category fields null in the response?

In the probe, the first record returned null for seller.feedback_pct, seller.feedback_count, category_path and return_policy, while the second record had a return policy and a category path. Treat these fields as optional in your parser, and use the seller profile operation when you need full seller reputation.

Related operations

Guides

View Subscription Plans →