---
title: "Akta.pro API / News"
description: "Akta tool akta-news on looot: input fields, $0.0005 per result, output shape, and code to run it with curl, JavaScript or Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

Fetch enriched news articles for a company or industry. Each article includes AI-generated summary, full text, sentiment, event tags, industry classifications, and resolved company mentions. Results are returned synchronously, with no polling.

- **Tool id:** `akta-news`
- **Provider:** [Akta](/providers/akta)
- **Job:** [Get recent news mentioning a company](/reference/jobs/company-news) (`company.news`)
- **Price:** $0.0005 per result. A call that fails at the provider costs $0.

## Inputs

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `blacklisted` | string | no |   |
| `company` | string | no |   |
| `countries` | string | no |   |
| `end_date` | string | no |   |
| `entity_event_list` | string | no |   |
| `entity_location_list` | string | no |   |
| `entity_person_list` | string | no |   |
| `entity_product_list` | string | no |   |
| `group_articles` | boolean | no |   |
| `iab_code_list` | string | no |   |
| `industry` | string | no |   |
| `iptc_code_list` | string | no |   |
| `limit` | integer | no |   |
| `naics_code_list` | string | no |   |
| `news_score_list` | string | no |   |
| `offset` | integer | no |   |
| `primary_company` | string | no |   |
| `query` | string | no |   |
| `sentiment_list` | string | no |   |
| `sic_code_list` | string | no |   |
| `start_date` | string | no |   |
| `title` | string | no |   |
| `type_list` | string | no |   |

## Output

Shape of the run's `result`, checked against 1 real answer:

```txt
{ data: { id, url, tags: { code, name, is_primary }[], title, author, entities: { event: unknown[], person: string[], product: string[], location: unknown[] }, group_id, countries: unknown[], full_text, publisher, sentiment, sic_codes: unknown[], ai_summary, industries: { code, name, is_primary }[], iptc_codes: { code, name }[], is_opinion, word_count, is_breaking, naics_codes: { code, name }[], article_type: { code, label }, iab_categories: { code, name }[], published_date, sentiment_score, company_mentions: { name, uuid, website, is_primary }[], is_press_release, original_language, newsworth... ...
```

The shape is cut here. Signed in, `looot inspect akta-news` prints all of it.

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With `wait: 30` the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll `GET /v1/runs/<runId>`.

Example input with placeholder values:

<CodeGroup>

```bash curl
curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"akta-news","input":{},"wait":30}'
```

```js JavaScript
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "akta-news",
    input: {},
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "akta-news",
        "input": {},
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To let looot pick among every provider of this job instead, send `job:company.news` as `endpointId`; see [the job page](/reference/jobs/company-news).