1. Home
  2. API

Developer access: pilot enquiries

Evaluate eBay sold-listing data for your workflow

Request a sample for your use case. We will confirm the available fields, coverage, and usage terms before you integrate.

The data

Sold-listing observations, without the dashboard

The Bayed app is built on records of eBay listings that sold: what the listing was, when it sold, and the price on the record. API access gives your application those observations directly, so you do not need to use the research screens at all.

Access is in pilot. We do not publish an endpoint or a response format here, because the fields and coverage are confirmed against your use case first.

What one observation describes

Listing
Title and item condition
Sale
Sold date and listing format
Price
Amount and currency on the sold record

This is the information the app works with. Your sample shows the exact field names, and which values can be missing.

What it is for

Workflows the pilot is meant for

  • Resale and inventory tools

    Show sold-price references next to the items your users are buying, listing, or holding.

  • Pricing workflows

    Feed sold observations for a product and condition into your own pricing rules.

  • Research and reporting

    Pull sold listings for a defined set of products and study them in your own tools.

Before you integrate

What your sample establishes

A sample is only useful if it answers the questions an integration depends on. Yours comes with notes on each of these.

  • Records

    What is a record?

    Whether a row is a listing, an observation of one, or a unit sold.

  • Amounts

    What does the amount mean?

    Which prices are final sale amounts, which are listing prices, and which are unavailable.

  • Status

    What does "sold" establish?

    The status eBay reported for the listing, and what it cannot confirm, such as a later return.

  • Scope

    What is covered?

    The marketplaces, filters, dates, and currencies available for your use case.

  • Freshness

    How fresh is it?

    When each record was collected and how refreshes work.

  • Paging

    How do I get more?

    How results are paged, and what a partial result looks like.

  • Errors

    What can fail?

    Empty results, errors, limits, and timeouts, with guidance on retries.

  • Billing

    What is billable?

    The unit you are charged for, and how empty or failed requests are treated.

  • Changes

    What changes over time?

    How changes to fields are announced and who to contact.

How the pilot works

From enquiry to integration

  1. Tell us the use case

    What you are building, the marketplace and fields you need, and roughly how much data.

  2. Review a sample

    We reply by email with a sample for your use case, or with questions if we need to narrow it down.

  3. Agree the terms

    We confirm fields, coverage, limits, and price by email before you write any integration code.

Request a sample

Tell us what you need the data for

The more specific the use case, the more useful the sample. We use these details to prepare it and to reply to you.

Prefer email?

Write to support@bayed.io with the same details.

Bayed is an independent service. It is not affiliated with, endorsed by, or sponsored by eBay Inc.

For example: a pricing screen in an inventory app for phone refurbishers.