Address types
Map company and representative address purposes to your address model
Company report addresses
companyReport.basicInformation.addresses contains addresses associated with the
reported company. The usual company address types are registered, business,
mailing, physical, and operations. Availability depends on the jurisdiction
and what its registry publishes.
The API reuses the same Address model and AddressType enum for companies,
people. The full enum shown in the API reference is therefore
not a field-specific allowlist or a promise that every type occurs in company
addresses. The schema accepts all enum values; registry classifications can also
produce less typical values, such as residential for an additional address
returned by Ireland's CORE registry.
Meanings and applicability
| Type | Meaning | Context |
|---|---|---|
registered | Address listed for the entity's registration, such as its registered office. | Company addresses; also organizational representatives or other registered parties. |
business | Address at which an entity conducts business, such as a principal office or branch. | Company addresses; also a representative's business address. |
mailing | Address at which an entity receives correspondence; may be a PO box. | Company or representative correspondence. Does not establish physical presence. |
physical | Location at which an entity has a physical presence. | Company or person addresses. Does not by itself establish a registered office or business premises. |
operations | Location where an entity operates. May identify only an operating community or locality. | Company operations, including operating locations of parties involved in trade. Does not guarantee a street address. |
residential | Address where an individual resides. | Usually a person, such as a legal representative, shareholder, or beneficial owner; may also be a source-classified company-associated address. |
placeOfBirth | Location where an individual was born. | Person data, including person.placeOfBirth; not a company office or residence. |
Company versus representative
Use the containing field to identify whose address you are reading. For example:
companyReport.basicInformation.addresses[]refers to the reported company.companyReport.relationships.legalRepresentatives[].person.addressrefers to an individual representative.companyReport.relationships.legalRepresentatives[].company.addressrefers to an organizational representative.
A representative's business address remains the representative's address;
it should not automatically become the reported company's business address.
Likewise, a company registered at someone's home can have a registered address:
the type describes the address's purpose in the record, not the building's use.
Mapping to your address model
Germany: legal seat versus business street address
The German Handelsregister distinguishes the Sitz (legal seat) from the
Geschäftsanschrift (business address). Our company reports map the seat to
registered, often with only a city, and the business address to business.
For example, a captured report for Eckes Pensions Verwaltungs GmbH contains:
| Type | Source address |
|---|---|
registered | Nieder-Olm |
business | Ludwig-Eckes-Platz, 1, 55268, Nieder-Olm |
If your system needs the company's main street address, the German business
address is the relevant candidate. Selecting registered alone can give you
only the legal-seat town. Neither type guarantees that an address is the actual
management headquarters, and the shared enum has no dedicated headquarters type.
For GmbHs, the distinction is reflected in §4a GmbHG and the separate registration of seat and business address in §10 GmbHG.
General mapping guidance
Match by type rather than by array position. Keep multiple addresses of the
same type: a registry can publish several premises or correspondence addresses.
Keep business, physical, and operations distinct unless your own model
deliberately combines them; none is an automatic substitute for registered.
type can be null or absent when no purpose is specified. Preserve such addresses
as unclassified, and handle any types your model does not recognize without
silently relabeling them. An absent or null addresses field does not prove that
the company has no address.
Use original for the source address text and normalized for structured
components when available. Addresses can be partial, and neither a type nor
structured components guarantee a complete postal delivery address. Retain
source when available to keep the registry provenance alongside your mapping.
Last updated on