> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openregister.de/llms.txt
> Use this file to discover all available pages before exploring further.

# Person information

## Get person information

Retrieve detailed information about a natural person including their name, date of birth, city of residence, age, and their roles across multiple companies. This endpoint aggregates data about a person's management positions, providing a complete profile of their business activities.

**Cost:** 10 credits

### Roles

Each entry in `management_positions` carries a `role_detail` — see [Roles](/roles).


## OpenAPI

````yaml GET /v1/person/{person_id}
openapi: 3.1.0
info:
  title: OpenRegister API
  version: 2.5.0
  description: >
    API for accessing comprehensive company data from official registers.

    This API provides access to company information, shareholder data, financial
    reports, and contact details.
servers:
  - url: https://api.openregister.de
    description: Production
security:
  - BearerAuth: []
paths:
  /v1/person/{person_id}:
    get:
      tags:
        - v1
      summary: Get detailed person information
      operationId: getPerson
      parameters:
        - name: person_id
          in: path
          description: The id of the person
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Successfully retrieved person data
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Person'
        '400':
          description: Bad Request - Invalid parameters provided
        '401':
          description: Unauthorized - Authentication required
        '402':
          description: Payment Required - Insufficient credits for this request
        '404':
          description: Not Found - Person ID doesn't exist
        '429':
          description: Too Many Requests - Rate limit exceeded
        '500':
          description: >-
            Internal Server Error - An error occurred while processing the
            request
      x-codeSamples:
        - lang: JavaScript
          source: >-
            import Openregister from 'openregister';


            const client = new Openregister({
              apiKey: process.env['OPENREGISTER_API_KEY'], // This is the default and can be omitted
            });


            const response = await
            client.person.getDetailsV1('182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e');


            console.log(response.id);
        - lang: Python
          source: |-
            import os
            from openregister import Openregister

            client = Openregister(
                api_key=os.environ.get("OPENREGISTER_API_KEY"),  # This is the default and can be omitted
            )
            response = client.person.get_details_v1(
                "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
            )
            print(response.id)
        - lang: Go
          source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\n\t\"github.com/oregister/openregister-go\"\n\t\"github.com/oregister/openregister-go/option\"\n)\n\nfunc main() {\n\tclient := openregister.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tresponse, err := client.Person.GetDetailsV1(context.TODO(), \"182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e\")\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", response.ID)\n}\n"
        - lang: CLI
          source: |-
            openregister person get-details-v1 \
              --api-key 'My API Key' \
              --person-id 182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e
components:
  schemas:
    Person:
      type: object
      properties:
        id:
          description: |
            Unique person identifier.
            Example: cc78ab54-d958-49b8-bae7-2f6c0c308837
          type: string
        first_name:
          description: |
            First name of the person.
          type: string
        last_name:
          description: |
            Last name of the person.
          type: string
        date_of_birth:
          description: |
            Date of birth of the person.
            Format: ISO 8601 (YYYY-MM-DD)
            Example: "1990-01-01"
          type: string
          format: date
          nullable: true
        age:
          description: |
            Age of the person.
          type: integer
          nullable: true
        city:
          description: |
            City of the person.
          type: string
        management_positions:
          description: |
            Management positions of the person.
          type: array
          items:
            $ref: '#/components/schemas/PersonManagementPosition'
            description: |
              All current and past management positions of the person.
      required:
        - id
        - first_name
        - last_name
        - date_of_birth
        - age
        - city
        - age
        - management_positions
    PersonManagementPosition:
      type: object
      properties:
        register_id:
          type: string
          description: |
            Register ID of the company.
            Example: DE-HRB-F1103-267645
        company_name:
          type: string
          description: |
            Name of the company.
            Example: "Descartes Technologies GmbH"
        role:
          type: string
          description: |
            Raw role string as stored, kept for backwards compatibility. It is
            register-level rather than bucketed, and for Prokura it carries a
            German string ("Einzelprokura", "Gesamtprokura", "Prokura").
            Prefer `role_detail`.
            Example: "EXECUTIVE"
          deprecated: true
        role_detail:
          $ref: '#/components/schemas/RepresentationRoleDetail'
          description: |
            The precise role as recorded in the register, plus ready-to-display
            titles. A Vorstand and a Geschäftsführer differ here.
        start_date:
          description: |
            Date when the person started the management position.
            Format: ISO 8601 (YYYY-MM-DD)
            Example: "2022-01-01"
          type: string
          format: date
        end_date:
          description: |
            Date when the person ended the management position.
            Format: ISO 8601 (YYYY-MM-DD)
            Example: "2023-01-01"
          type: string
          format: date
      required:
        - register_id
        - company_name
        - role
        - role_detail
        - start_date
    RepresentationRoleDetail:
      description: |
        The register-level role behind the coarse `role` bucket, together with
        display-ready titles in German and English. Always present.
      type: object
      properties:
        code:
          $ref: '#/components/schemas/RepresentationRoleDetailCode'
          description: |
            The precise role as recorded in the register.
            Example: "EXECUTIVE" for a Vorstand, "DIRECTOR" for a
            Geschäftsführer — both have role "DIRECTOR".
        label_de:
          description: |
            German title, gender-neutral, as shown on openregister.de.
            Example: "Vorstand"
          type: string
        label_de_short:
          description: |
            Abbreviated German title, for dense layouts such as tables.
            Example: "Vst."
          type: string
        label_en:
          description: |
            English title. A translation for display, not a legal term — the
            German title is the one the register uses.
            Example: "Executive Board Member"
          type: string
        label_en_short:
          description: |
            Abbreviated English title, for dense layouts such as tables.
            Example: "Exec. Board"
          type: string
      required:
        - code
        - label_de
        - label_de_short
        - label_en
        - label_en_short
    RepresentationRoleDetailCode:
      description: |
        Register-level role code. Unlike `role`, this set grows as new roles
        appear in the register. Treat an unrecognised value as OTHER and match
        on `role` if you need an exhaustive set.
      type: string
      enum:
        - DIRECTOR
        - EMERGENCY_DIRECTOR
        - EXECUTIVE
        - CHAIRMAN
        - DEPUTY_CHAIRMAN
        - BOARD
        - PRESIDENT_BOARD
        - VICE_PRESIDENT_BOARD
        - PRESIDENT
        - MEMBER
        - NON_EXECUTIVE_DIRECTOR
        - BOARD_SECRETARY
        - BOARD_TREASURER
        - BOARD_SPORTS
        - BOARD_OTHER
        - REPRESENTATIVE
        - SECONDARY_REPRESENTATIVE
        - COURT_ORDERED_REPRESENTATIVE
        - PROKURA
        - PROKURA_SINGLE
        - PROKURA_JOINT
        - LIQUIDATOR
        - INSOLVENCY_DIRECTOR
        - PRELIMINARY_INSOLVENCY_DIRECTOR
        - OWNER
        - SHAREHOLDER
        - PARTNER
        - PERSONAL_LIABLE_DIRECTOR
        - OTHER
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: |
        API Key Authentication
        Provide your API key as a Bearer token in the Authorization header.

````