German Company LEI Status Monitor

Search and monitor public GLEIF records for German legal entities, including LEI status, legal name, address, registration data, changes, and source evidence. German-language onboarding, due-diligence, enrichment, and compliance-review teams. Monitor changes to German legal-entity identifiers and return a source-linked evidence trail for review queues.

What it does

This Actor normalizes the supported evidence into a default Apify dataset and keeps the original source reference with each buyer-visible result. Its buyer-value event is change-alert; it uses Apify pay-per-event pricing, so inspect the current Pricing tab and begin with a small validation run.

Supported sources and boundary

• GLEIF LEI API for public German legal-entity records

Only the sources and buyer inputs listed above are supported. The Actor does not bypass login, CAPTCHA, paywalls, robots restrictions, private APIs, or any other access control. It is an independent tool and is not affiliated with the named source platforms or authorities.

Inputs

• buyerQuery — Company name, LEI, or German legal-entity monitoring scope.
• watchlistTerms — German company names or LEI values to watch.
• maxItems — Maximum matching records to write.

Existing saved-task fields remain accepted for backward compatibility. Use Apify's maximum run-charge limit for any live validation run.

Buyer-ready output

• lei
• legalName
• entityStatus
• registrationStatus
• registeredAddress
• registrationAuthority
• sourceUrl
• retrievedAt

Every output preserves source provenance where the input or public source provides it. Unsupported sources return an explicit boundary error instead of an invented record.

First run

{
    "sourceMode": "sample",
    "buyerQuery": "Deutsche LEI Status pr\u00fcfen",
    "maxItems": 1
}

The bundled first-run example is a labelled deterministic demonstration, not proof of current live coverage:

{
    "evidenceType": "deterministic_demo",
    "legalName": "Beispiel Deutsche Gesellschaft",
    "lei": "52990000000000000000",
    "entityStatus": "ACTIVE"
}

API, dataset, schedules, and webhooks

Use the Apify API or default dataset for programmatic retrieval. Save an input as an Apify task to schedule recurring runs. If the current input schema exposes webhookUrl, it can notify a buyer-controlled endpoint after a completed run; otherwise use Apify webhooks for the task or run.

Common use cases

• Build a source-linked internal review queue.
• Compare repeated signals across a buyer watchlist.
• Export normalized JSON or CSV for an approved downstream workflow.

Limitations and responsible use

GLEIF is the built-in source in this version. It is not a comprehensive German register or licensing service; verify official records before taking action.

Support

Include the Actor run ID, the input field names (not secrets), an example source URL when authorized, and the observed output field when contacting Zentra support. Check the current Pricing and API tabs before production-scale runs.