/ground_news/stories/top

POST /api/ground_news/stories/top

Price: 20 credits

Get the Ground News top stories feed for a regional edition (US, International, UK, Canada, Europe). Each story card carries the political-bias distribution (left/center/right coverage percentages and source counts), blindspot info, factuality and ownership distribution of the covering sources, geography, topics and a per-source list.

How to use it

Fetch the Ground News home / top stories feed. Choose edition (US, International, UK, Canada, Europe) and count. Each item is a news story with title, generated_headline, description, the bias distribution (left_percent/center_percent/right_percent and source counts), blindspot_for, factuality and ownership source counts, place, interests and sources.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• edition string — Regional edition of the top feed (default: "us"; one of: "us", "international", "uk", "canada", "europe")
• count integer required — Max number of stories to return (min: 1)

Response

• @type string (default: "GroundNewsStoryCard")
• id string required
• slug string required
• generated_headline string nullable
• description string nullable
• dek string nullable
• summary string nullable
• start string nullable
• image string nullable
• source_count integer nullable
• bias_source_count integer nullable
• left_percent number nullable
• center_percent number nullable
• right_percent number nullable
• left_src_count integer nullable
• cntr_src_count integer nullable
• right_src_count integer nullable
• blindspot_for string nullable
• blindspot_statement string nullable
• coverage_profile_type string nullable
• factuality object nullable
  • @type string (default: "GroundNewsFactuality")
  • very_high integer nullable
  • high integer nullable
  • mixed integer nullable
  • low integer nullable
  • very_low integer nullable
  • unknown integer nullable
• ownership object nullable
  • @type string (default: "GroundNewsOwnership")
  • telecom integer nullable
  • private_equity integer nullable
  • media_conglomerate integer nullable
  • billionaire integer nullable
  • government integer nullable
  • independent integer nullable
  • corporation integer nullable
  • other integer nullable
  • uncategorized integer nullable
• place array (default: [])
  • @type string (default: "GroundNewsPlace")
  • id string nullable
  • name string required
  • type string nullable
• interests array (default: [])
  • @type string (default: "GroundNewsInterest")
  • id string nullable
  • name string required
  • alias string nullable
  • type string nullable
  • image string nullable
• sources array (default: [])
  • @type string (default: "GroundNewsSourceArticle")
  • source_id string nullable
  • source_name string required
  • source_alias string nullable
  • interest_id string nullable
  • bias string nullable
  • factuality string nullable
  • image string nullable
  • description string nullable
  • reference_url string nullable
  • date string nullable
  • is_opinion boolean (default: false)
  • bias_ratings array (default: [])
    • @type string (default: "GroundNewsBiasRating")
    • reviewer string required
    • political_bias string nullable
    • reference_url string nullable
  • owners array (default: [])
    • @type string (default: "GroundNewsOwner")
    • id integer nullable
    • name string required
    • category 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 — 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.