Do I have to change my code to migrate?

In almost all cases the only change is the host name. Paths, query parameters and response field names are identical, and the axesso-api-key header keeps working, so even the header can stay. Swap the key value for your everydata.io key and you are done.

Are the response envelopes really the same?

Yes. responseStatus and responseMessage come first (PRODUCT_FOUND_RESPONSE for the shops, PAGE_FOUND for Home Depot, Naver, Zillow and YouTube). Amazon 404s use the vnd.error array, other shops return {statusCode: 404, statusMessage}.

Which platforms are covered?

Amazon, Walmart, Zalando, Otto, Kaufland, Lidl, ASOS, Home Depot, Naver, Zillow, Yahoo Finance and YouTube, plus the Amazon Deals dataset download and the account quota endpoint. The path list above is complete for the marketplace APIs.

Can I run both providers in parallel during migration?

That is what we recommend: point a share of traffic at everydata.io, compare responses field by field, then switch the base URL for the rest. The free plan is enough for a side-by-side test.

Do failed requests cost quota?

No. Upstream 5xx or blocked responses (502/503) are refunded and never count towards your monthly quota. Successful responses and client errors (4xx) do.

Is everydata.io affiliated with Axesso?

No. everydata.io is an independent service operated from Germany. Axesso is a trademark of its owner; we reference it only to describe compatibility.

Comparison & migration guide

everydata.io as an Axesso alternative

everydata.io implements the same endpoint structure as the Axesso Data Service: identical paths, identical query parameters, identical response field names. This page lists what stays the same, what is different and how to switch – so you can make the decision on facts rather than marketing.

Test with a free key OpenAPI reference

Migration

Migration is a base-URL change

Swap the host and the key value. The header name can stay, the paths do not change.

Before

bash

curl -s "https://api.axesso.de/amz/amazon-lookup-product?url=https://www.amazon.com/dp/B07ZPKN6YR?psc=1" \
  -H "axesso-api-key: $AXESSO_API_KEY"

After – only the host changes

bash

curl -s "https://api.everydata.io/amz/amazon-lookup-product?url=https://www.amazon.com/dp/B07ZPKN6YR?psc=1" \
  -H "x-api-key: $EVERYDATA_API_KEY"

The response is the same JSON you already parse: responseStatus and responseMessage first, then productTitle, manufacturer, countReview, productRating, asin, soldBy, retailPrice, price, features, imageUrlList and the rest. Run both providers side by side for a day, diff the payloads, then flip the host for the remaining traffic.

Authentication & errors

Headers, keys and status codes

Topic	Axesso	everydata.io
API key header	axesso-api-key: <key>	x-api-key: <key> – the axesso-api-key header is accepted as well
API key as query parameter	?axesso-api-key=<key>	?apiKey=<key> (works, but prefer the header – query strings end up in access logs)
RapidAPI	x-rapidapi-key / x-rapidapi-host	Supported when you subscribe through RapidAPI; same paths
Missing or invalid key	401 {statusCode, message}	Identical body and status
Quota exhausted	403 Out of call volume quota	403 {statusCode: 403, message}
Rate limit	429 Rate limit is exceeded. Try again in N seconds.	Identical
Upstream failure (target site 5xx / blocked)	Varies	502/503 {statusCode, statusMessage}; not counted against your quota

Every response carries an additional X-Response-Time-Ms header. Quotas and rate limits are plan-based; see pricing.

Path mapping

Same prefix, same paths, for every platform

All paths are identical, including the platform prefix. The table lists the prefixes; the endpoint pages list every path.

Platform	Prefix	Endpoints	Mapping
Amazon	/amz	11	identical · plus /amazon-lookup-product-by-asin and /amazon-price-history
Walmart	/wlm	3	identical
Zalando	/zal	2	identical
Otto	/ott	3	identical
Kaufland	/kfl	3	identical
Lidl	/ldl	3	identical
Asos	/aso	3	identical
Home Depot	/hod/v1	3	identical
Naver	/nav/v1	2	identical
Zillow	/zil	12	identical
Yahoo Finance	/yho	11+ (46 operations)	identical · 4 retired endpoints return 501
YouTube	/ytb	9+ (18 operations)	identical

Known differences

What behaves differently – and what to do about it

A compatible API is not a clone. These are the deviations we know of; each has a straightforward workaround.

Amazon reviews (/amz/amazon-lookup-reviews)

Amazon only serves the full paginated review listing to signed-in sessions. When the listing is empty we return the top reviews embedded in the product page instead: responseStatus stays PRODUCT_FOUND_RESPONSE, responseMessage explains the fallback, lastPage is 1 and star/keyword filters are not applied. If you paginate reviews, check responseMessage and lastPage.

Amazon deals (/amz/amazon-search-deals-v2)

Pages map 1:1 onto Amazon's deals grid with 30 deals per page. countDeals and lastPage are derived from the grid actually returned, so they can differ from what you saw before. Iterate until the deals array is empty rather than trusting a fixed lastPage. Filters are validated against /amz/amazon-deal-filter-v2.

Yahoo Finance – four retired endpoints

/yho/market-get-watchlist-detail, /yho/market-get-watchlist-performance, /yho/conversations-count and /yho/conversations-v2-list return 501 NOT_IMPLEMENTED because Yahoo no longer offers these publicly. They are marked deprecated in the OpenAPI document; remove the calls or handle the 501.

Yahoo Finance response shapes

Responses keep Yahoo's native JSON (quoteSummary.result[], finance.result, chart.result[] …). A few operations are lightly shaped, e.g. /stock-v3-get-historical-data returns a prices[] array.

Zillow output=xlsx

Not supported and answered with 400. output=csv and output=json work. /search-by-polygon is deprecated in favour of POST /search-by-polygon-v2, as before.

Caching parameters (new, opt-in)

cacheTtl on Amazon, Zalando and ASOS product lookups and withCache on searches let you accept cached data (up to 24 h / 10 min). The default stays realtime, so existing integrations behave the same.

New Amazon endpoints

/amz/amazon-lookup-product-by-asin (asin + domainCode instead of a URL) and /amz/amazon-price-history (price observations collected by everydata.io) have no Axesso counterpart. Everything else is optional to adopt.

Legacy Amazon endpoints

/amz/amazon-search-by-keyword (ASIN list) and /amz/sort-options are kept for old integrations; new code should use /amz/amazon-search-by-keyword-asin.

Why switch at all

What you gain, stated plainly

Failed fetches are free

Upstream 5xx and blocked responses are refunded automatically. Your quota pays for data, not for retries.

Opt-in caching

cacheTtl and withCache let you trade freshness for speed and cost on the calls where a few minutes do not matter.

Price history for Amazon

The /amz/amazon-price-history endpoint gives you observations we already collected – useful for trackers that start from zero.

One quota for everything

All twelve platforms share a single key and plan. Adding Walmart or Zillow to an Amazon integration needs no new contract.

EU-operated

Operated from Germany; account data is hosted in the EU and only publicly available data is processed.

Self-service plans

Free plan with 100 requests, paid plans from €30 a month, monthly cancellation and Stripe invoices.

Axesso is an established provider with its own strengths. If your integration relies on one of the deviations above and you cannot adapt it, staying is a perfectly reasonable choice.

FAQ

Migration questions

Run a side-by-side test in five minutes

Create a free key, replay a handful of your existing requests against the new host and diff the JSON.

Get your free API key