Latvia Enterprise Register Public Search

Extract Latvia Enterprise Register company and business records for company discovery, business research and directory exports. Latvia Enterprise Register Public Search collects public information into one complete dataset table, ready to export as Excel, CSV or JSON.

Use search filters, set how many results you need and start the Actor. Search returns the fields made available in this service’s public results.

At a glance	Details
📥 Input	Search filters
📋 Collection modes	Search companies
📤 Output	One row per record, or a failed row for an unsuccessful input
📄 Pagination	Automatic, up to maxResults while more records are available
🔐 Website login	Not required
💾 Export	One dataset view with all fields; Excel, CSV and JSON

What the Latvia Enterprise Register scraper collects 📋

Mode	What you receive
Search companies	Matching company and business records and the fields published in the search results.

The field table and complete examples below show the information this Actor returns. Optional values depend on what the source publishes for the selected record.

Coverage for this Actor:

• Latvian register search only. Search can match current names, previous names and addresses. Detailed profiles require an access check and are not included.
• Name search uses approximate matching and may return similar names when an exact name has no matches.

How to scrape Latvia Enterprise Register 🚀

1. Choose Search companies.
2. Complete the search filters.
3. Set Maximum results. The minimum is 1.
4. Start the Actor and review the saved dataset.
5. Export the results or connect them to your workflow.

Search companies — input example

{
  "mode": "search",
  "keywords": "auto",
  "maxResults": 150
}

maxResults limits all saved rows for each search or supplied record, including a failed row. It does not guarantee that the source has that many matching records.

Latvia Enterprise Register data fields and complete output 📦

Each result stays in one row. Every returned field appears in the same dataset view, including list fields and additional published facts. Fields unavailable for a particular record remain empty.

Field	Included data
result_type	Selected collection mode.
input	Submitted search settings, record link or record number.
status	Record processing status.
error_code	Failure category for an unsuccessful input.
error_message	Readable explanation for an unsuccessful input.
record_id	Stable source identifier.
source_id	Source id, when published.
registration_number	Registration number, when published.
name	Registered or published name.
short_name	Short name, when published.
address	Address, when published.
company_status	Company status, when published.
registration_date	Registration date, when published.
registry_entry_date	Registry entry date, when published.
legal_form	Legal form, when published.
register_code	Register code, when published.
has_insolvency_record	Has insolvency record, when published.
has_partnership_record	Has partnership record, when published.
entity_type	Entity type, when published.
previous_addresses	Previous addresses, when published.
previous_names	Previous names, when published.
previous_short_names	Previous short names, when published.
termination_date	Termination date, when published.
additional_fields.name	Names of additional published fields, when present.
additional_fields.value	Their corresponding values in the same order.

The complete result below is included for every mode. Text and lists are not shortened. These are examples from validation runs; the source can change.

Search companies — complete JSON result

{
  "result_type": "search",
  "input": "{\"keywords\": \"auto\"}",
  "status": "success",
  "record_id": "020342445",
  "source_id": "020342445",
  "registration_number": "40203424454",
  "name": "SIA \"GK CARGO\"",
  "short_name": "GK CARGO",
  "address": "Aizkraukles nov., Aizkraukles pag., \"Auto Kardāns\"",
  "company_status": "REGISTERED",
  "registration_date": "2022-09-06T00:00:00Z",
  "registry_entry_date": "2022-09-06T00:00:00Z",
  "legal_form": "SIA",
  "register_code": "K",
  "has_insolvency_record": false,
  "has_partnership_record": false,
  "entity_type": "lventity",
  "previous_addresses": null,
  "previous_names": null,
  "previous_short_names": null,
  "termination_date": null,
  "additional_fields.name": [],
  "additional_fields.value": []
}

Input settings ⚙️

Setting	What to enter
What to collect (mode)	Choose the information you need.
Maximum results per search or link (maxResults)	Collect up to this many saved results for each search or record link. Minimum: 1.
Company name (keywords)	Enter a company name or words. The register may return approximate matches, including previous names and addresses.

Latvia Enterprise Register scraping use cases 🎯

Build a company research list

Use the supported name, category or location fields to collect relevant companies. Export the available business information with source references.

Compare matching company records

Review the business information published in the search results. This Actor does not include a separate record details mode.

Keep a business dataset current

Schedule repeated exports and compare stable company IDs. Missing fields remain empty instead of being guessed.

Pricing and saved-result behavior 💰

See the Actor’s Pricing tab for the current rate. Under dataset-item pricing:

• Each saved record is one result. Lists and additional details attached to it do not create extra rows.
• A saved failed row is also one billable dataset item. This includes invalid inputs, unavailable records, empty searches and exhausted retries.
• At most one failed row is saved per input. Retry attempts do not create additional dataset rows.
• maxResults caps all saved rows for the input. Duplicate copies of the same input are processed once.

Latvia Enterprise Register scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","keywords":"auto","maxResults":150}'

Use Apify schedules for recurring collection, webhooks for completion notifications, and integrations for Google Sheets, Make, Zapier, cloud storage or your own application.

Reliability and public-data limits ⚠️

Temporary request failures are retried up to five total attempts. Invalid record inputs save a failed row without a website request. Confirmed missing records are not retried unnecessarily. If a later request fails, records already saved remain in the dataset. Normal pagination completion does not add a failed row. Collection stops after two consecutive pages return no new records. Configuration, data-saving or request-scheduling failures stop the run.

Latvia Enterprise Register controls the available records and fields. Search records can contain less information than a full public card. The Actor preserves published values and does not fill missing facts with estimates.

Frequently asked questions ❓

Do I need a Latvia Enterprise Register account?

No. This Actor collects the supported public information without your website login.

Which search filters can I use?

The input form supports company name. Only the displayed filters are supported.

How many records can I collect?

Set maxResults to the maximum saved rows you want for each input. The minimum is 1. Collection can finish earlier when the source runs out of results or stops returning new records.

Why are some fields empty?

The source may not publish a value for that record or mode. Optional information remains empty.

Can I export all the fields?

Yes. All returned fields are included in one dataset view. Nested lists remain attached to their parent record.

Support 🛟

For a reproducible issue, share the run ID, selected mode and a safe public example through the Actor’s support channel. Keep tokens, passwords and proxy credentials private.