Quantexa (Aylien) News API → APITube migration kit

For teams whose code still calls api.aylien.com/v6/news/*. Parameter tables, response field mapping, a drop-in shim for Node.js and Python, and an AI prompt that rewrites your queries.

Every APITube claim here was executed against the live API before being written down. The Quantexa side comes from the official v6 documentation as archived on 19 June 2025 — because, as of 27 July 2026, it is no longer online.

Read this first: the API is not reachable

docs.aylien.com and api.aylien.com no longer resolve. Checked against Cloudflare's resolver (1.1.1.1) on 27 July 2026:

Domain	DNS
docs.aylien.com	NXDOMAIN
api.aylien.com	NXDOMAIN
aylien.com	Domain exists, no A record
quantexa.com	Resolves

Their own status page at aylien.statuspage.io still reads "All Systems Operational" with no incidents, so the public health indicator disagrees with DNS. There is no formal end-of-life announcement — only the February 2023 acquisition, the rebrand from AYLIEN News API to Quantexa News API, and the company's own note that some previously well-served use cases are "no longer as strong a fit".

If your integration still works, you are calling something this kit cannot verify. Treat every Quantexa-side detail below as documentation-derived, not tested.

What you were using

Endpoints (v6): /v6/news/stories, /v6/news/clusters, /v6/news/histograms, /v6/news/time_series, /v6/news/trends, plus /v2/autocomplete/suggestions/{entity-names,entity-types,sources}.

Auth: OAuth bearer token from https://api.aylien.com/v1/oauth/token. Older versions used X-AYLIEN-NewsAPI-Application-ID and X-AYLIEN-NewsAPI-Application-Key headers.

Limits: 60 requests per minute (three per second), per_page up to 100, cursor-based paging via next_page_cursor, 16 languages.

Categories: the same taxonomy, but only the top level transfers

Quantexa classified stories with IPTC MediaTopics — the taxonomy APITube also uses — alongside IAB categories. The codes are the same numbers; APITube prefixes them with medtop:.

That makes top-level filters a mechanical rename:

Quantexa	APITube	Verified
01000000	medtop:01000000	✅
04000000	medtop:04000000	✅
13000000	medtop:13000000	✅

Child codes are a different story. APITube's category list holds 1 085 codes — 17 top-level and 1 068 children — but the children are concentrated in the 20000xxx branch. Quantexa's finer codes from other branches are not there:

# 400 ER0206 "category with ID 'medtop:01005000' not found."
curl "https://api.apitube.io/v1/news/everything?api_key=YOUR_API_KEY&category.id=medtop%3A01005000"

# 400 ER0206
curl "https://api.apitube.io/v1/news/everything?api_key=YOUR_API_KEY&category.id=medtop%3A01005001"

So: rename the top-level codes mechanically, and check every child code individually against the category list before relying on it. Where a child code is missing, its parent is the honest fallback — broader results, not wrong ones.

IAB categories (IAB1, IAB1-2) have no APITube equivalent at all.

What else does not carry across neatly: their Aylien Query Language (aql), cursor paging, the clusters and time-series endpoints, and sentiment.*.polarity as a label rather than a score.

Quick comparison

	Quantexa News API v6	APITube
Availability	Domains do not resolve	Live
Per request	100 stories	250
Paging	Cursor (next_page_cursor)	page + per_page
Rate limit	60/minute	50/minute paid, 10/minute free
Languages	16	No Russian or Ukrainian; see the language table
Categories	IPTC MediaTopics + IAB	IPTC MediaTopics — top level maps, children need checking
Sentiment	positive / neutral / negative label per axis	Signed score per axis, plus per-entity
Entities	Wikidata-linked, with prominence and surface forms	Wikidata-linked, with frequency and per-entity sentiment
Auth	OAuth bearer token	X-API-Key header

What is in here

Path	What it gives you
reference/parameter-mapping.md	Every /v6/news/stories parameter → its APITube equivalent
reference/endpoint-mapping.md	All five endpoints, and what replaces the three that have no direct counterpart
reference/limitations.md	What does not carry over, plus live APITube quirks
shim/node/	QuantexaShim — accepts /v6/news/stories parameters, returns the Quantexa response shape
shim/python/	Same shim for Python
examples/	Before/after request pairs
tools/ai-migration-prompt.md	System prompt for Claude/ChatGPT that converts your queries

Quick start

# Quantexa News API v6 (documented form — the host no longer resolves)
curl "https://api.aylien.com/v6/news/stories?title=tesla&language=en&per_page=100" \
  -H "Authorization: Bearer YOUR_TOKEN"

# APITube
curl "https://api.apitube.io/v1/news/everything?title=tesla&language.code=en&per_page=250" \
  -H "X-API-Key: YOUR_API_KEY"

License

MIT. Use it, fork it, ship it.