---
title: "News events discover"
description: "Run job:discover.news-events through the looot API: 1 provider, from $0.01 per result. Inputs, prices, output shape and code for curl, JavaScript and Python."
sidebar:
  hidden: true
---

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

News events discover.

Job id `discover.news-events`, in [Enrichment](/catalog/enrichment) (Company discovery). As of 2026-10-01, 1 provider serve it through 1 tool. Run `job:discover.news-events` and looot picks one of them; with `fallback` on, a miss moves on to the next. See [Jobs](/concepts/jobs).

## Inputs

This job has one tool, so it takes that tool's fields. Any key you send passes through unchanged.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `categories` | array | no | One or more valid categories as a comma-separated string (e.g. `param=val1,val2`) or as array parameters (e.g. `param[]=val1&param[]=val2`). |
| `company_location` | string | no | The response will include only results in the given country name or state name/abbreviation. Example: "United States" |
| `company_sizes` | array | no | One or more valid company sizes as a comma-separated string (e.g. `param=val1,val2`) or as array parameters (e.g. `param[]=val1&param[]=val2`). |
| `limit` | integer | no | Limit the number of shown items per page. |
| `page` | integer | no | Page number of shown items. **NOTE**: If the parameter is not provided, the meta property `count` will be omitted from response for performance reasons. |

## Providers and prices

| Provider | Tool | Price |
| --- | --- | --- |
| [PredictLeads](/providers/predictleads) | [`predictleads-discover-news-events`](/reference/tools/predictleads-discover-news-events) | $0.01 per result |

A call that fails at the provider costs $0. See [What's free](/money/free-and-failures).

## Output

Shape of the run's `result`, the expected shape, not yet checked against real answers:

```txt
{ data: { id, type, attributes: { event, summary, category, found_at, planning, confidence, product_data: { ... }, effective_date, article_sentence }, relationships: { company1: { ... }, most_relevant_source: { ... } } }[], meta: { record_state, schema_version }, included: { id, type, attributes: { domain, company_name } }[] }
```

## 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":"job:discover.news-events","input":{"company_location":"United States"},"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: "job:discover.news-events",
    input: {
      company_location: "United States",
    },
    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": "job:discover.news-events",
        "input": {
            "company_location": "United States",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To pin one provider, send its tool id as `endpointId` instead of `job:discover.news-events`.