/dw/authors

POST /api/dw/authors

Price: 1 credit

Get one Deutsche Welle journalist profile by url or person id: full name, area of expertise, biography, portrait and social handle.

How to use it

author accepts a full DW url, a path, or a bare id in the form 'person-18542747'; a plain number also works. Person ids come from an article's authors[].id. Journalists who write for several editions have a separate profile id per edition. For their stories call dw/authors/articles. Base url is https://www.dw.com.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• author string required — DW author profile url, path or bare person id (examples: "https://www.dw.com/en/mark-hallam/person-18542747", "person-18542747"; minLength: 1)
• language string — DW language edition, used when the identifier carries no language segment (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: "DwAuthor")
• id integer required
• name string required
• alias string nullable
• language string nullable
• profile_url string nullable
• expertise string nullable
• text string nullable
• teaser string nullable
• social_description string nullable
• twitter_handle string nullable
• image object nullable
  • @type string (default: "DwImage")
  • id integer nullable
  • image string nullable
  • name string nullable
  • caption string nullable
  • credit string nullable
  • image_type string nullable
• is_auto_delivery boolean nullable
• is_indexed boolean nullable
• is_rtl boolean 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 — No DW author profile with this id in this language edition 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.