Handelsregister.ai German Person Profile API

Use the Handelsregister.ai German Person Profile API to retrieve a person profile linked to a German company, including documented roles and optional holdings or network data. Supply the documented company, person, document, or signal identifiers and optional controls shown in the parameter reference. Use the result to research German businesses, support onboarding checks, reconcile company records, or follow register changes. Requests use your Handelsregister.ai account credentials, and some features require a subscription. The detail page includes request examples, available response illustrations, supported parameters, and fixed usage pricing based on the documented maximum credit cost.

Selected price
$0.494505 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Person name.
Company where the person holds or held a registered role.
Comma-separated shareholdings (+5) and network (+25, Pro/Max). Plus subscription or above is required for the endpoint; unsupported network is silently omitted.
Per logical request idempotency key: 1–128 ASCII letters/digits/dot/underscore/colon/hyphen; starts with letter or digit. Reuse only with identical parameters. The legacy query/header validator enforces length but delegates the exact pattern to the provider.

Sample response

{
  "affiliations": [
    {
      "organization": "ENSoXX Holding AG",
      "relation": "Vorstandsmitglied"
    },
    {
      "organization": "Hetzner Online GmbH",
      "relation": "Geschäftsführer"
    },
    {
      "organization": "ENSoXX hilft e.V.",
      "relation": "Vorstandsmitglied"
    },
    {
      "organization": "TRAIDY UG (haftungsbeschränkt)",
      "relation": "Geschäftsführer"
    },
    {
      "organization": "HT clean energy GmbH",
      "relation": "Geschäftsführer"
    },
    {
      "organization": "DreamSoXX GmbH",
      "relation": "Geschäftsführer"
    },
    {
      "organization": "Lighthouse GmbH",
      "relation": "Prokura"
    },
    {
      "organization": "ENSoXX GmbH",
      "relation": "Geschäftsführer"
    },
    {
      "organization": "ENSoXX Invest GmbH",
      "relation": "Geschäftsführer"
    },
    {
      "organization": "Sonnenkraft Merkendorf GmbH & Co. KG",
      "relation": "Kommanditist"
    },
    {
      "organization": "Modellsportclub Gunzenhausen e.V.",
      "relation": "Vorstandsmitglied"
    },
    {
      "organization": "possum Projekt 1 GmbH",
      "relation": "Prokura"
    }
  ],
  "bio": "Max Felix Mustermann ist Geschäftsführer der Hetzner Online GmbH und Unternehmer im Bereich Rechenzentren.",
  "birth_date": "1976-01-15",
  "contact": {
    "emails": [
      {
        "address": "[email protected]",
        "label": "Allgemeine Unternehmenskontakt-E-Mail",
        "type": "organization"
      },
      {
        "address": "[email protected]",
        "label": "E-Mail für Produktfeedback",
        "type": "organization"
      }
    ],
    "phones": [
      {
        "entity": "Hetzner Online GmbH",
        "label": "Öffentliche Unternehmens-Telefonnummer",
        "number": "+49374574447100",
        "type": "organization"
      },
      {
        "entity": "Hetzner Online GmbH",
        "label": "Öffentliche Unternehmens-Telefonnummer",
        "number": "+49911234226100",
        "type": "organization"
      },
      {
        "entity": "Hetzner Online GmbH",
        "label": "Zentrale Unternehmensnummer",
        "number": "+4998315050",
        "type": "organization"
      }
    ]
  },
  "entity_id": "08ed5f967956831ca6588930fd2693ed",
  "expertise": [
    "Rechenzentren",
    "Hosting"
  ],
  "handelsregister_roles": [
    {
      "end_date": "2015-07-28",
      "entity_id": "94eb910fef13f94585c48c263fa446d4",
      "label": "BOARD",
      "name": "Hetzner Online GmbH",
      "role": {
        "de": "Vorstandsmitglied",
        "en": "Board Member"
      },
      "start_date": "2002-10-15"
    },
    {
      "end_date": "2015-07-28",
      "entity_id": "0b3435f83ce8591300625100815d4583",
      "label": "BOARD",
      "name": "Hetzner Online GmbH",
      "role": {
        "de": "Vorstandsmitglied",
        "en": "Board Member"
      },
      "start_date": "2002-10-15"
    },
    {
      "end_date": null,
      "entity_id": "0b3435f83ce8591300625100815d4583",
      "label": "MANAGING_DIRECTOR",
      "name": "Hetzner Online GmbH",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2015-07-28"
    },
    {
      "end_date": null,
      "entity_id": "94eb910fef13f94585c48c263fa446d4",
      "label": "MANAGING_DIRECTOR",
      "name": "Hetzner Online GmbH",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2015-07-28"
    },
    {
      "end_date": null,
      "entity_id": "dd1cfcd3a25b5a63d549d768e2fcaaaf",
      "label": "MANAGING_DIRECTOR",
      "name": "ENSoXX GmbH",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2015-08-14"
    },
    {
      "end_date": null,
      "entity_id": "58d67a0bb99b2bc5644cb8daba58e6a6",
      "label": "BOARD",
      "name": "ENSoXX Holding AG",
      "role": {
        "de": "Vorstandsmitglied",
        "en": "Board Member"
      },
      "start_date": "2016-02-03"
    },
    {
      "end_date": null,
      "entity_id": "bc1c1e106ade810eb960c779d4c752a8",
      "label": "BOARD",
      "name": "ENSoXX hilft e.V.",
      "role": {
        "de": "Vorstandsmitglied",
        "en": "Board Member"
      },
      "start_date": "2017-02-24"
    },
    {
      "end_date": null,
      "entity_id": "b34f5fcc114e7d4c5fe9d5f6f8fb0d10",
      "label": "MANAGING_DIRECTOR",
      "name": "TRAIDY UG (haftungsbeschränkt)",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2022-03-14"
    },
    {
      "end_date": "2026-08-12",
      "entity_id": "4cd425f9ad57d6119f704ba53131b480",
      "label": "BOARD",
      "name": "Modellsportclub Gunzenhausen e.V.",
      "role": {
        "de": "Vorstandsmitglied",
        "en": "Board Member"
      },
      "start_date": "2023-06-06"
    },
    {
      "end_date": null,
      "entity_id": "0e8b1b4fc27a3ecc07d397750505e7b5",
      "label": "MANAGING_DIRECTOR",
      "name": "ENSoXX Invest GmbH",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2023-12-13"
    },
    {
      "end_date": null,
      "entity_id": "2ab71b59057969183dd811adf9f32ebd",
      "label": "MANAGING_DIRECTOR",
      "name": "HT clean energy GmbH",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2024-08-20"
    },
    {
      "end_date": null,
      "entity_id": "260286ab8baa3a8977fddd56b9361c6c",
      "label": "MANAGING_DIRECTOR",
      "name": "DreamSoXX GmbH",
      "role": {
        "de": "Geschäftsführer",
        "en": "Managing Director"
      },
      "start_date": "2025-01-13"
    },
    {
      "end_date": null,
      "entity_id": "7582db1f94e1538ba8f531f6a95a7f1b",
      "label": "PROCURA",
      "name": "Lighthouse GmbH",
      "role": {
        "de": "Prokura",
        "en": "Procura"
      },
      "start_date": "2025-03-25"
    },
    {
      "end_date": null,
      "entity_id": "232d2ed634eef59eb21836cc47cb5645",
      "label": "LIMITED_PARTNER",
      "name": "Sonnenkraft Merkendorf GmbH & Co. KG",
      "role": {
        "de": "Kommanditist",
        "en": "Limited Partner"
      },
      "start_date": "2026-02-18"
    },
    {
      "end_date": null,
      "entity_id": "64922d416b4dd7006f3c2c62efaabd5d",
      "label": "PROCURA",
      "name": "possum Projekt 1 GmbH",
      "role": {
        "de": "Prokura",
        "en": "Procura"
      },
      "start_date": "2026-09-04"
    },
    {
      "end_date": null,
      "entity_id": "997f1b8314b8b56573208ae2334abb1d",
      "label": "PROCURA",
      "name": "possum Projekt 1 GmbH",
      "role": {
        "de": "Prokura",
        "en": "Procura"
      },
      "start_date": "2026-09-04"
    }
  ],
  "location": {
    "home": {
      "city": "Musterheim"
    }
  },
  "meta": {
    "credits_remaining": 145,
    "request_credit_cost": 15
  },
  "name": "Max Felix Mustermann",
  "name_parts": {
    "canonical_name": "Mustermann, Max Felix",
    "family": "Mustermann",
    "given": "Max Felix",
    "maiden": null,
    "previous_names": null
  },
  "profiles": {
    "linkedin": null,
    "other": []
  }
}

Response result

Response structure

Inferred from examples
  • affiliationsobject[]
    • organizationstring
    • relationstring
  • biostring
  • birth_datestring
  • contactobject
    • emailsobject[]
      • addressstring
      • labelstring
      • typestring
    • phonesobject[]
      • entitystring
      • labelstring
      • numberstring
      • typestring
  • entity_idstring
  • expertisestring[]
  • handelsregister_rolesobject[]
    • end_datestring | null
    • entity_idstring
    • labelstring
    • namestring
    • roleobject
      • destring
      • enstring
    • start_datestring
  • locationobject
    • homeobject
      • citystring
  • metaobject
    • credits_remaininginteger
    • request_credit_costinteger
  • namestring
  • name_partsobject
    • canonical_namestring
    • familystring
    • givenstring
    • maidennull
    • previous_namesnull
  • profilesobject
    • linkedinnull
    • otherunknown[]

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Handelsregister.ai German Person Profile API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.