/dw/topics/search

POST /api/dw/topics/search

Price: 1 credit

Browse the Deutsche Welle topic catalogue alphabetically. Returns topics of one language edition with id, name, alias, browse url and the index group they are filed under — one chosen group, or the whole catalogue across every group of the edition.

How to use it

Discover DW topic ids without guessing. Leave group empty to walk the whole catalogue of an edition — every entry names its own group, which is how you learn an edition's alphabet: Arabic, Greek, Hindi and Chinese editions file topics under their own scripts, so a Latin letter finds nothing there. Set group once you know which letter you want. Feed an id into dw/topics or dw/topics/articles.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• group string nullable — Index group to list — a single letter of the edition's own alphabet, or 'numbers' / 'hashtag'. Omit to walk every group of the edition in order (examples: "a", "numbers", "hashtag")
• count integer required — Number of topics to return (min: 1)
• language string — DW language edition (default: "en"; one of: "de", "en", "ar", "es", "ru", "fr", "uk", "tr", "fa-ir", "fa-af", "ps", "ur", "hi", "bn", "pt-br", "pt-002", "pl", "ro", "sr", "bs", "hr", "mk", "sq", "bg", "el", "zh", "zh-hant", "id", "sw", "ha", "am")

Response

• @type string (default: "DwTopicIndexEntry")
• id integer required
• name string required
• alias string nullable
• url string nullable
• group string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — This DW edition has no such index group Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.