Linking GLEIF (Global Legal Entity Identifier Foundation) as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
This source is currently in alpha. The interface and available tables may change.
The GLEIF (Global Legal Entity Identifier Foundation) connector syncs lei records, lei issuers, entity legal forms, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
None. The GLEIF (Global Legal Entity Identifier Foundation) API is public, so no account or API key is needed.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Import Legal Entity Identifier (LEI) reference data from GLEIF's free, public registry. No API key or account is required.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All GLEIF (Global Legal Entity Identifier Foundation) tables are full refresh. Each sync replaces the contents of the table.
Configuration
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
LeiRecords | A Legal Entity Identifier (LEI) record: the legal name, address, jurisdiction, status, and registration details of one legally distinct entity. | Incremental, Full refresh | last_update_date | — |
LeiIssuers | A Local Operating Unit (LOU) accredited by GLEIF to issue and maintain LEIs. | Full refresh | — | — |
EntityLegalForms | A jurisdiction's entity legal form (e.g. LLC, GmbH) from the ISO 20275 code list. | Full refresh | — | — |
RegistrationAuthorities | An official business registry (e.g. a companies house) recognized by GLEIF. | Full refresh | — | — |
Countries | An ISO 3166-1 country used to classify LEI records and legal forms. | Full refresh | — | — |
Jurisdictions | An ISO 3166-2 jurisdiction (country or country subdivision) used to classify LEI records. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.