/axios/audiences

POST /api/axios/audiences

Price: 5 credits

List the Axios audiences a story can be written for — the national desk and every Axios Local city edition. Each audience carries its identifier, slug, display name, kind, local timezone, default paywall state, whether its stories and jobs are open to everyone, and which of stories, jobs and ticketed events its newsroom currently publishes.

How to use it

List Axios audiences. count says how many to return. Each item has id, alias (the city or desk slug), name, audience_type, timezone, default_paywall_status, has_public_stories, has_public_jobs, sells_events, publishes_stories, publishes_jobs, publishes_events and requires_salary_on_jobs. Feed id into axios/topics/articles as audience_ids to browse one city edition or the national desk.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of audiences to return (min: 1)

Response

• @type string (default: "AxiosAudienceDetail")
• id string required
• alias string required
• name string nullable
• audience_type string nullable
• timezone string nullable
• default_paywall_status string nullable
• has_public_stories boolean nullable
• has_public_jobs boolean nullable
• sells_events boolean nullable
• publishes_stories boolean nullable
• publishes_jobs boolean nullable
• publishes_events boolean nullable
• requires_salary_on_jobs 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 — The entity was not found, or a precondition failed 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.