European keyword discovery
Mit Qwant-Endpunkten verwandelst du european keyword discovery in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Retrieve Qwant autocomplete phrases for an English, French, German, British, Italian, Dutch, or other well-formed market locale, preserving the engine's order without implying full Qwant SERP coverage.
Collect Qwant-ranked autocomplete suggestions by prefix and European market locale as structured JSON for query research workflows.
Endpunkt-Familien
1
Dokumentierte Parameter
4
Beispiele
1
Live-Katalog-Snapshot
Aktive Endpunkte
1
Methoden
GET
Pflichtparameter
2
Schema-Referenzen
1
{
"platform": "Qwant",
"endpoint": "qwant-suggest",
"method": "GET",
"path": "/qwant/suggest",
"auth": "apiKey"
}Use Cases
Collect Qwant-ranked autocomplete suggestions by prefix and European market locale as structured JSON for query research workflows.
Mit Qwant-Endpunkten verwandelst du european keyword discovery in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Qwant-Endpunkten verwandelst du localized query expansion in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Qwant-Endpunkten verwandelst du autocomplete monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Qwant-Endpunktkatalog — 1 Endpunkte, 4 dokumentierte Request-Parameter und 1 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
1 documented Qwant endpoints, all in the Suggest family.
4 request parameters are documented across those Qwant endpoints, 2 of them required — the full input contract is public before you write any integration code.
1 of the 1 Qwant endpoints ship a recorded example response, and 1 carry a documented response schema — you can code against the real JSON before the first request.
Qwant endpoints document their error responses (400, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
1 hosted MCP tool backs the Qwant endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/qwant/suggest
Endpunktkatalog
/qwant/suggestReturns Qwant search-box autocomplete completions for a query prefix, in Qwant's own ranking order. `locale` selects the Qwant market (en_US, fr_FR, de_DE, en_GB, ...); Qwant ignores locale codes it does not support and uses its default market.
Hinweise zur Response
- Qwant re-ranks the list for the markets it supports and silently treats an unsupported well-formed locale as its default market; only the format is validated here. - A prefix with no completions returns a valid empty `suggestions` array, not an error.
MCP-Tool qwant_suggest
Verwandte APIs
Search & Web Discovery
Use a Google Trends API — an API for Google Trends data — to track search demand, trending terms, interest over time, regional interest, related and rising queries, plus Google Suggest discovery, as structured JSON for demand research and trend monitoring.
Search & Web Discovery
Extract Google News results — headlines, source names, article URLs, snippets, thumbnails, and recency — as structured JSON for media monitoring, brand mention tracking, and news aggregation workflows.
Search & Web Discovery
Extract Google Jobs results — job titles, listing snippets, and locations — as structured JSON for job-market intelligence, hiring-trend analysis, and recruitment sourcing workflows.
So scrapst du Qwant
Qwant presents itself as a French-developed search engine with privacy-by-design and unprofiled results, supported by its own indexing technology and partners. Crawlora's current public catalog exposes Qwant autocomplete only, not full web results. Send a required prefix plus an optional ll_CC market locale and count up to 10; the response preserves Qwant's ranking. A supported locale can re-rank the list, while a well-formed but unsupported locale silently uses Qwant's default market.
Send q to /qwant/suggest. Use a partial phrase that reflects the language and subject you want to expand rather than a complete question.
Pass locale in ll_CC form, such as en_US, en_GB, fr_FR, de_DE, it_IT, or nl_NL. The parameter defaults to en_US; malformed locale syntax returns 400.
Set count from 1 to 10 and retain position with each suggestion. A supported market can reorder or change the phrases, so record locale alongside every observation.
A valid prefix with no Qwant completions returns an empty suggestions array. That differs from malformed parameters and transport or upstream errors.
FAQ
No. The current public catalog contains /qwant/suggest only. It returns Qwant's autocomplete phrases and positions, not organic result URLs or snippets.
Use ll_CC, such as en_US or fr_FR. The format is validated, but Qwant can silently use its default market when a syntactically valid locale is unsupported.
On 2026-10-06, the English prefix privacy with en_US returned phrases such as privacy & security and privacy concerns with ai wearables. In a separate request, the French prefix vie privée with fr_FR returned phrases such as vie privée et familiale. Because both query and locale changed, these dated examples do not isolate a locale effect or define fixed vocabularies.
No claim is made that it does. Qwant's official pages describe Qwant's own privacy practices. A request to Crawlora uses Crawlora's API, authentication, billing, and terms; the endpoint returns supported public autocomplete data.