# Finland Trade Register Filing Events (`nexgenwatch/finland-trade-register-filing-events`) Actor

- **URL**: https://apify.com/nexgenwatch/finland-trade-register-filing-events.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $13.40 / 1,000 registry records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Finland Trade Register Filing Events

One structured `registry_record` per record from proven public sources, logged-out. Public, robots-honoured.

Difference: one registry\_record per PUBLIC NOTICE ROW (a trade-register filing event) on the official PRH open-data registered-notices API, filtered by a notice-date window (noticeRegistrationDateStart/End — July 2026 = 38,355 companies with a notice in-window). Company Business ID + name and the notice's record number, type of registration, entry codes and registration date are carried verbatim. This is the date-windowed filing-EVENT stream — a different job from the finland-prh-ytj-company-registry roster (the full company master) and the finland-prh-business-filing-lookup single-entity check.

### What you get

One `registry_record` per entity/notice, deduplicated on the source-native id. Fields the sources do not publish are honest `null`. A `run_receipt` row carries the source URLs, scope, reconciliation counts, and delivered/duplicate totals.

### How it behaves

Companies with a public notice in the requested window are paged 50/page from the PRH registered-notices API; each company's public-notice rows dated in the window are expanded to one record each, deduped on Business ID + record number + date. Notice fields are carried verbatim. count reconciled against the API's totalResults (companies-in-window). Streaming, bounded to maxRecords; memory bounded.

### Attribution

Contains data from the Finnish Patent and Registration Office (PRH), reused under the PRH open-data licence. Each `run_receipt` and the actor README carry this attribution.

### Source

`https://avoindata.prh.fi/opendata-registerednotices-api/v3/`

### Pricing

| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
| `apify-actor-start` (one-time actor start) | $0.02 | $0.02 | $0.02 | $0.02 |
| `registry_record` (per unique record) | $0.02 | $0.018 | $0.016 | $0.0134 |

Charged once per unique record delivered. Start fee $0.02.

# Actor input Schema

## `maxRecords` (type: `integer`):

maxRecords (buyer bound).

## `noticeRegistrationDateStart` (type: `string`):

noticeRegistrationDateStart.

## `noticeRegistrationDateEnd` (type: `string`):

noticeRegistrationDateEnd.

## `userAgent` (type: `string`):

userAgent.

## Actor input object example

```json
{
  "maxRecords": 300
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxRecords": 300
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/finland-trade-register-filing-events").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxRecords": 300 }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/finland-trade-register-filing-events").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxRecords": 300
}' |
apify call nexgenwatch/finland-trade-register-filing-events --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/finland-trade-register-filing-events"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZUpuUNQxdFNw06Voc/builds/mqTGA08cDLZhndRk6/openapi.json