🔔 Latvia Annual-Report Financial Statements

One record per filed annual-report statement (company number, statement id, period, type, employees, currency) streamed from the 205 MB official CSV, bounded to your maxRecords — no full-file download.

Public, robots-honoured, keyless.

Output is one lv_financial_statement row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: data.gov.lv.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run uVF5yGsalZ5YooM3K on build 0.1.6 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

file_id	legal_entity_registration_number	source_schema	period_start	period_end	created_at
16544390	40103504912	DokGPUIENv1	2016-01-01	2016-12-31	2020-10-30 23:33:27.773
16544392	40103466358	DokGPUIENv1	2016-01-01	2016-12-31	2020-10-30 23:33:31.502
16544401	40103476182	DokGPUIENv1	2016-01-01	2016-12-31	2020-10-30 23:33:34.353
16544404	40103863270	DokUGP2008v1	2015-01-21	2015-12-31	2020-10-30 23:33:37.364
16544411	40008010613	DokGPUIENv1	2016-01-01	2016-12-31	2020-10-30 23:33:40.692
16544413	40103693358	DokGPUIENv1	2016-01-01	2016-12-31	2020-10-30 23:33:43.794
16544422	40003770970	DokUGP2008v1	2015-01-01	2015-12-31	2020-10-30 23:33:46.868
16544424	40103458882	DokGPUIENv1	2016-01-01	2016-12-31	2020-10-30 23:33:49.818

The run finished with the status message: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. lv_financial_statement
• statement_id (string/null) — e.g. 709390
• file_id (string/null) — e.g. 16544390
• legal_entity_registration_number (string/null) — e.g. 40103504912
• statement_type (string/null) — e.g. UGP
• source_schema (string/null) — e.g. DokGPUIENv1
• year (string/null) — e.g. 2016
• period_start (string/null) — e.g. 2016-01-01
• period_end (string/null) — e.g. 2016-12-31
• employees (string/null) — e.g. 0
• rounded_to_nearest (string/null) — e.g. ONES
• currency (string/null) — e.g. EUR
• created_at (string/null) — e.g. 2020-10-30 23:33:27.773
• source (string/null) — e.g. latvia-financial-statements
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://data.gov.lv/dati/dataset/8d31b878-536a-44aa-a013-8bc6b669d477/resource/2
• observed_at (string/null) — e.g. 2026-09-18T06:15:46Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

What you get

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

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "maxRecords": 50
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 50 × $0.02 registry_record = $1.02 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
  "maxRecords": 2000
}

Up to 2000 rows (the schema default for maxRecords) — about $40.02 on the Free tier ($0.02 start + 2000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run uVF5yGsalZ5YooM3K, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "lv_financial_statement",
  "statement_id": "709390",
  "file_id": "16544390",
  "legal_entity_registration_number": "40103504912",
  "statement_type": "UGP",
  "source_schema": "DokGPUIENv1",
  "year": "2016",
  "period_start": "2016-01-01",
  "period_end": "2016-12-31",
  "employees": "0",
  "rounded_to_nearest": "ONES",
  "currency": "EUR",
  "created_at": "2020-10-30 23:33:27.773",
  "source": "latvia-financial-statements",
  "release_date": null,
  "source_url": "https://data.gov.lv/dati/dataset/8d31b878-536a-44aa-a013-8bc6b669d477/resource/27fcc5ec-c63b-4bfd-bb08-01f073a52d04/download/financial_statements.csv",
  "observed_at": "2026-09-18T06:15:46Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

The official financial_statements.csv is streamed row-by-row and stopped at maxRecords, so a run transfers only the leading bytes it needs. Header drift, a truncated read, or an HTML error page fail loud and charge nothing.

Source

https://data.gov.lv/dati/dataset/8d31b878-536a-44aa-a013-8bc6b669d477/resource/27fcc5ec-c63b-4bfd-bb08-01f073a52d04/download/financial_statements.csv

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry record (registry_record)	$0.02	$0.02	$0.02	$0.01

Worked at the live Free-tier price:

• 8 registry records: $0.02 start + 8 × $0.02 = $0.18
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 2000 registry records: $0.02 start + 2000 × $0.02 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 50 unique rows (0 duplicates collapsed). billable=50. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by data.gov.lv. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (data.gov.lv) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers data.gov.lv. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Czech ARES Company Registry — One structured registryrecord per record from the keyless ares.gov.cz REST economic-subjects API, logged-out. Public, logged-out, robots-honoured
• Estonia Company Registry (bulk) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Latvia Company Registry (bulk) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• NY OCM Licence Registry — One structured registryrecord per record from the New York Office of Cannabis Management licence dataset (keyless NY Socrata jskf-tt3q, ~2,927 rows).…
• NYC DCWP Business Licence Registry — One structured registryrecord per record from the NYC Open Data DCWP licences resource (Socrata w7w3-xahh, ~69,885 rows). Public, logged-out, robots-…
• Poland KRS Company Registry — One structured registryrecord per record from the keyless api-krs.ms.gov.pl current-extract JSON (OdpisAktualny), logged-out. Public, logged-out, rob…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.