Handelsregister.ai German Register Document Download API

Use the Handelsregister.ai German Register Document Download API to download an official German company register document as PDF or structured XML. 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.164835 / 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
32-hex company entity_id, not a company name. Exact hexadecimal pattern is validated upstream.
PDF except SI, which is XJustiz XML. Some originals may be unsupported TIFF.
Optional 202 polling mode. A 202 is not file delivery and costs 0 credits; retry the same request after Retry-After. HTTP 200 delivers the raw file.
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

{
  "meta": {
    "credits_remaining": 145,
    "message": "The document is being retrieved. Repeat this request after Retry-After seconds to receive it.",
    "request_credit_cost": 0,
    "retry_after": 20
  },
  "status": "processing"
}

Response result

Response structure

Inferred from examples
  • metaobject
    • credits_remaininginteger
    • messagestring
    • request_credit_costinteger
    • retry_afterinteger
  • statusstring

Loading related APIs…

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 Register Document Download API with your agent

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