Any data.One API.On demand.

Try a live request.

Fire a real query hitting the production API. Change the parameters and see exactly what comes back.

Get a price estimate.

I'm tracking 1,000 records, refreshed daily .

One key. One call.

There's no SDK to learn — it's an HTTP endpoint. Set one header and the language you already use is enough.

# the whole integration
curl "https://api.trawl.dev/ebay/v1/sold?query=iphone+15+pro" \
  -H "x-api-key: $TRAWL_KEY"

Questions, answered.

No sales call required — the answers developers actually check for.

How is this different from marketplace APIs?

Most are thin wrappers that break without notice. trawl APIs are engineered products: typed responses, stable schemas, monitored uptime — one team accountable for all of it.

What counts as a request?

One successful call — a 2xx response. Failed or rate-limited calls don't spend anything.

Do I need a credit card to start?

No. Sign up with an email, grab a key, start calling. Upgrade only when you need the volume.

Which marketplaces are covered?

eBay US and eBay UK today. New sources are prioritized by demand — drop a URL in the box above and we'll build it.

What does each record carry?

Title, sold price, shipping, condition, sold date and a link to the listing — typed JSON with field names that hold still.

What happens when I hit my limit?

Requests return 429 until the month resets. Upgrading in the console lifts the cap immediately.

Is there an SDK?

Not yet — and you don't need one. It's plain HTTP with an x-api-key header, so every language's stdlib (or curl) already works.