Repository navigation
Point the Handelsregister adapter at the handelsregister.ai v1 API - #1606
Merged
Merged
Conversation
The adapter called /search and /companies/{id}, which do not exist
(404 on every call since the adapter was added), and sent the key as
Authorization: Bearer. The API documents /search-organizations,
/fetch-organization and /fetch-document with the key in x-api-key.
Shareholders come from fetch-organization's shareholders feature, and
hr_get_documents becomes hr_fetch_document (one document per call).
helpcodeai
enabled auto-merge (squash)
November 9, 2026 09:34
Add fetch-person, signals (list, one, topic catalog) and the free account endpoints (profile, credits, usage, subscription), the realtime_mode/ai_search options of fetch-organization and match_context in search. Rename the tools to the handelsregister_ prefix the validator asks for: they never worked, and installed connectors need a reinstall for the new auth header anyway.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Handelsregister (handelsregister.ai) catalog adapter never worked: every call answered 404 since it was added in April. It used
/searchand/companies/{company_id}, which handelsregister.ai does not have. A paying Cloud customer reported it today (search and company lookups both 404). Production confirms it: the 2 calls ever made on the 2 installed connectors both failed with 404.The documented API (https://handelsregister.ai/en/documentation) is
/v1/search-organizations,/v1/fetch-organization(with optionalfeatures) and/v1/fetch-document, with the API key in thex-api-keyheader. Checked without a key: the old/searchanswers 404, the three new paths answer 401 "provide a valid API key (via x-api-key header ...)".Changes
x-api-key: {{HANDELSREGISTER_API_KEY}}instead ofAuthorization: Bearer(Bearer is for scoped tokens, not API keys).handelsregister_prefix (the oldhr_names gave validator warnings; they never worked, and installed connectors need a reinstall for the new auth header anyway):handelsregister_search_companies→GET /search-organizations(q,filtersJSON,limitmax 30,skip,sort,order,match_context)handelsregister_get_company→GET /fetch-organization(company_idasq, comma-separatedfeatures,financial_statement_type,financial_years,realtime_mode,ai_search)handelsregister_get_shareholders→fetch-organizationwithfeatures=shareholdershandelsregister_fetch_document→GET /fetch-document(AD, CD, SI, shareholders_list, articles_of_association); replaceshr_get_documents, there is no list endpointhandelsregister_fetch_person→GET /fetch-person(person_q,organization_q,feature)handelsregister_list_signals,handelsregister_get_signal,handelsregister_list_signal_topics→/signals,/signals/{id},/signals/catalog(only the 5 list parameters the API accepts; any other answers 422)handelsregister_get_account,_get_credits,_get_usage,_get_subscription→ the free/accountendpointsde/handelsregister.live.spec.ts: static checks of auth, every path and the signals parameters; live check of/account(0 credits) behindRUN_HANDELSREGISTER_LIVE=1.Type
Testing
From the root:
node scripts/validate-adapters.mjs --warn(0 warnings for this adapter; before: 5),node scripts/regenerate-catalog.mjs(no diff),node scripts/adapter-count.mjs --checkOK (715 adapters, 12,924 tools),node scripts/generate-llms-txt.mjs(no diff). Inpackages/backend:npx jest src/adapters722 suites passed, 25,716 tests passed (live specs skipped), eslint clean on the spec. Manual, at zero credit cost: without a key the old/searchanswers 404 and all 11 new paths answer 401; with the reporting customer's key (decrypted only inside the Cloud backend, never printed) oneGET /accountinx-api-keyanswered 200 withrequest_credit_cost: 0. The paid endpoints were not called with a key.Checklist
npm test)Related Issues
None. Customer support request, 2026-11-09.
Cloud and self-hosted: same adapter.
endpointMappingand auth changes are structural, so installed connectors get them after "Apply update" in the "Catalog update available" box on the connector page.