Israel Companies Registrar — Status, Type & Address Lookup

Israel Companies Registrar — Status, Type & Address Lookup

Look up Israeli companies via the official data.gov.il companies registrar (Rasham HaChavarot / רשם החברות — the Israeli government's open-data mirror of the companies register). Get back company name, legal type, current status (active / dissolved / in liquidation / etc.), registered address, and incorporation date. No login, no manual portal search, no API key.

What it does

This actor queries the government's own open-data CKAN API (data.gov.il/api/3/action/datastore_search) — a free, keyless, official public dataset, not a scrape of a locked page. Results are returned as clean JSON dataset items, one row per company, with a parse_confidence field for quality.

Use cases

• Verify an Israeli counterparty's registration status before signing a contract.
• Lead generation and market research — pull a filtered slice of active companies.
• Compliance / KYB checks — confirm a company number resolves to an active, non-dissolved entity.
• Feeding pipelines, dashboards, and AI agents with fresh structured company data.

Input

Field	Type	Default	Notes
companyName	string	""	Free-text search across the Hebrew and English name fields (e.g. "eToro").
companyNumber	string	""	Exact Israeli company number (e.g. 515240497) — a unique lookup. Overrides the filters below.
activeOnly	boolean	true	Only return companies whose current status is exactly "active" (פעילה). Ignored when companyNumber is set.
city	string	""	Exact registered-address city filter, in Hebrew as the registry stores it (e.g. "תל אביב - יפו").
sortRecentFirst	boolean	true	Sort by company number descending — biases results toward recently-registered companies.
maxResults	integer	20	Cap on records returned (1–10,000).

A gotcha we already found (and fixed by default)

The registry's raw row order (its internal import/insertion order, not a registration-date index) surfaces very old records first when you query with no filter — some of them companies from the 1930s, long dissolved, with blank address fields. This is a sampling artifact of the dataset's default order, not a real data gap — the same dataset holds millions of fully-populated, currently-active companies (recognisable names like eToro Group Ltd, incorporated 2017, show up immediately once you ask correctly). The default input already applies both fixes:

1. activeOnly: true — filters to the exact "active" status.
2. sortRecentFirst: true — sorts by company number descending (company numbers are assigned sequentially at registration, so this is a reliable "newest first" proxy).

Together, the default sample returns real, well-populated, currently-active companies — never the old dissolved shells.

Output fields

Each record includes the company identity (number, Hebrew + English name, legal type), current status and sub-status, stated purpose, incorporation date, government-ownership flag, registered address (street, house number, city, ZIP, P.O. box, country), last annual-report year filed, and a parse_confidence score.

A note on the registered_care_of field: the registry sometimes carries a "c/o" (אצל) name at the registered address — a publicly-mandated disclosure of who holds the company's registered address, the same category of public officer/registered-agent disclosure this fleet already surfaces for the German commercial register (Handelsregister). It is not incidental personal data — it's what Israeli company law already requires be public.

Pricing

Pay-per-event (PPE): one charge per company record (company-record) delivered to the dataset. (No price has been set live yet — see the build report for the proposed figure.)

Data source

Data comes from Israel's official open-data portal, mirroring the government companies registrar — the same authoritative source used for legal/compliance lookups — so results are accurate and require no credentials or scraping of a locked portal.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.