How to get a single article by ID#

To fetch the full content of one article when you already know its ID, call the /v1/news/article endpoint with the id parameter. The endpoint returns the same complete article object you get from search — title, body, source, entities, sentiment and the rest — for the IDs you ask for. This fetches one article:

curl "https://api.apitube.io/v1/news/article?id=1234567&api_key=YOUR_API_KEY"

You can pass the key as the api_key query parameter or as an X-API-Key header. The id you pass is the same id value returned in every search and retrieval result, so the typical flow is: run a search, store the id of an article, then re-fetch its full content later by ID.

How do I fetch several articles at once?#

Pass a comma-separated list of IDs to the id parameter and the endpoint returns one object per matching article in the results array. A single call accepts up to 100 IDs — anything beyond the first 100 is dropped, so split larger batches across multiple requests:

curl "https://api.apitube.io/v1/news/article?id=1234567,1234568,1234569&api_key=YOUR_API_KEY"

The endpoint accepts both GET (IDs as a query parameter) and POST (IDs in a JSON body); the two are equivalent. A POST example:

curl -X POST "https://api.apitube.io/v1/news/article" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "id": "1234567,1234568" }'

What does the article endpoint return?#

/v1/news/article returns the same JSON envelope as the search endpoints — status, the pagination fields (limit, page, has_next_pages, next_page, has_previous_page, previous_page), an export block of ready-made download URLs, and request_id — wrapping a results array with one full article object per ID found. Because you fetch by ID, has_next_pages is always false (there is no next page to page into):

{
  "status": "ok",
  "limit": 100,
  "page": 1,
  "has_next_pages": false,
  "next_page": "",
  "request_id": "b4c8e19f-2a6d-47c3-9e15-8f2b0d7a4c63",
  "results": [
    {
      "id": 1234567,
      "href": "https://example.com/some-story",
      "title": "...",
      "published_at": "2026-06-20T08:00:00.000Z",
      "language": "en",
      "body": "...",
      "source": { "domain": "example.com" },
      "sentiment": { "overall": { "polarity": "positive" } }
    }
  ]
}

Each object carries the standard article fields, including id, href, published_at, title, description, body, body_html, language, author, image, categories, topics, industries, entities and source. If an ID does not match any article, it is simply absent from results — the endpoint does not raise an error for unknown IDs, so a request with three IDs where one is missing returns two objects.

How to return only the fields you need#

If you only need part of the article object, add the fl parameter with a comma-separated list of field paths. This trims the response to those fields, which keeps payloads small when you fetch many IDs:

curl "https://api.apitube.io/v1/news/article?id=1234567&fl=id,title,href,published_at&api_key=YOUR_API_KEY"

How much does fetching an article by ID cost?#

Each /v1/news/article call costs 1 credit, regardless of how many IDs you pass in one request — fetching 100 articles in a single call costs the same one credit as fetching one. You are only charged when at least one article is returned: if none of the IDs match, no credit is spent. For a quick way to size a result set before fetching, see How to count news articles without downloading them.

Common Questions#

• Can I fetch more than 100 articles in one call?
• Why is the article body truncated?
• What errors can the article endpoint return?
• Where do I get the article ID?

Can I fetch more than 100 articles in one call?#

No. A single /v1/news/article request keeps only the first 100 IDs from the id list and ignores the rest. To fetch more, break your IDs into batches of 100 and send one request per batch.

Why is the article body truncated?#

Article content is masked on Free-plan keys and on test keys (the ones starting with api_test_). Both return a truncated body with an upgrade marker instead of the full text, so you can preview the shape of the response without revealing full content. Use a live key on a paid plan to receive the complete body and body_html.

What errors can the article endpoint return?#

The most common ones are: ER0232 (HTTP 400) when the id parameter is missing, ER0201/ER0202 (HTTP 401) when the API key is missing or invalid, and ER0176 (HTTP 402) when your account has no credits left. Each error response includes the request_id to help you trace the call.

Where do I get the article ID?#

Every search and retrieval result includes an id field — that value is what you pass to /v1/news/article. Run any query from the Searching & Filtering News section, read the id from each result, and re-fetch the full article later by that ID.