Company Registry Pages & Export Cleaner
Pricing
from $1.20 / 1,000 successful supplier checks
Company Registry Pages & Export Cleaner
Collect supported public company-registry pages or validate supplied company exports. API-backed Czech, Norwegian, French and Spanish registry adapters are unavailable.
Pricing
from $1.20 / 1,000 successful supplier checks
Rating
0.0
(0)
Developer
Inus Grobler
Maintained by CommunityActor stats
1
Bookmarked
14
Total users
6
Monthly active users
14 days ago
Last modified
Categories
Security
Limited permissionsShare
Company Registry Pages & Company Export Cleaner
Clean, validate and deduplicate your company registry exports into an Apify dataset. Provide JSON records or an Apify dataset ID. This workflow processes evidence you already have and labels its provenance clearly.
Quick start
- Replace the demonstration JSON with your records.
- Set maxResultsPerCountry to a small processing limit.
- Start the Actor and open the default dataset.
For a dataset, clear providedRecords to [] and enter providedDatasetId instead. Use one source at a time. Only records you are authorized to process should be supplied.
{"providedRecords": [{"companyName": "Owned demonstration company","jurisdiction": "GB","country": "United Kingdom","registryName": "Customer supplied export","sourceUrl": "https://example.com/owned-company/1","searchQuery": "owned demonstration","isNew": false,"isChanged": false,"scrapedAt": "2026-10-01T00:00:00Z","contentHash": "e59983f104a658a49e72e337c0359eb8a241ad7cb508e9ba0ba876a9ce2790cb"}],"maxResultsPerCountry": 1}
What you receive
One row per accepted record, using the established output fields. Text is cleaned, records are checked against the output field types, and duplicates are excluded. Missing values are not filled with invented counters, dates or native website identifiers. An observed zero stays zero.
Rows include dataInputSource="provided", sourceVerified=false, sourceRecordHash and dataProcessedAt. The hash identifies processed content; it is not a website ID. Processing does not verify the original source, ownership claims, freshness or factual accuracy.
PROVIDED_DATA_SUMMARY in the run key-value store reports accepted, rejected, duplicate and confirmed delivered counts. Dataset read limits and incomplete scans are disclosed. Diagnostics are not paid dataset rows.
Collection availability
Supported public HTML collection remains available. API-backed sources are unavailable. Existing input fields remain accepted for integrations, but they do not trigger a source API or another Actor. Without supplied data, existing page-based input fields select live HTML collection. Unsupported API-only sources report source failures and deliver no replacement result rows. GB and other implemented HTML registry routes remain available. Czech ARES, Spanish OpenBORME, French registry-search and Norwegian Brreg API adapters are disabled. Provided monitoring flags and content hashes are customer assertions; normalization does not update their monitoring baseline.
Pricing and limits
Check the Actor Pricing tab for current charges. Each delivered primary record uses the existing result event. Start fees and platform usage may still apply to empty or failed runs. Start with one record; the input limit bounds records scanned, including rejected records and duplicates.
Python API example
from apify_client import ApifyClientclient = ApifyClient("YOUR_APIFY_TOKEN")run = client.actor("thescrapelab/global-company-registry-lead-finder").call(run_input={"providedDatasetId": "YOUR_DATASET_ID","maxResultsPerCountry": 1,})if run is None:raise RuntimeError("Actor did not return run metadata")dataset_id = run["defaultDatasetId"] if isinstance(run, dict) else run.default_dataset_idfor record in client.dataset(dataset_id).iterate_items():print(record)
Troubleshooting
- No valid rows: inspect rejection codes and check the documented fields and types.
- Only part of a dataset read: increase the processing limit and review sourceDatasetLimited in the summary.
- Inaccessible dataset: use a 17-character ID and an Apify token with read access.
- Unsupported live mode: supply your existing records; adding source credentials does not enable collection.
Open the Issues tab with a run ID and a sanitized example for support.
Output example
Illustrative output; replace source values with your own authorized evidence.
{"companyName": "Owned demonstration company","jurisdiction": "GB","country": "United Kingdom","registryName": "Customer supplied export","sourceUrl": "https://example.com/owned-company/1","searchQuery": "owned demonstration","isNew": false,"isChanged": false,"scrapedAt": "2026-10-01T00:00:00Z","contentHash": "e59983f104a658a49e72e337c0359eb8a241ad7cb508e9ba0ba876a9ce2790cb","dataInputSource": "provided","sourceVerified": false}