Support
Where to ask, and what to include so the answer is useful.
Getting in touch
| Sales, trials, raising your request allowance | sales@registercheck.de |
| Technical problems | support@registercheck.de |
| Shared Slack Connect channel | Ask your account contact |
Before you write
Most questions are answered faster by one of these:
- A
429on a key that worked yesterday is usually the monthly request allowance, not the key. - An empty list of shareholders, roles or financial statements is usually coverage, not a bug.
- A
500from monitoring is usually a duplicate monitor or an unknownevent_typesvalue — see Monitoring.
What to include
For anything we have to reproduce:
- The full request URL, with parameters, and the method.
- The response status and body.
- The company or person id, if the question is about specific data.
- A timestamp with a timezone, so we can find the request in our logs.
Please do not send us your API key. If you believe a key has leaked, revoke it on the Usage (API & Nutzung) page and tell us afterwards.
Reporting wrong data
Register data can be wrong for two different reasons, and it helps to say which you think it is:
- We disagree with the register. Tell us the company id and what the register says. These are extraction faults and we can fix them.
- The register itself is wrong or out of date. We cannot correct the register. The company must file a correction with its Amtsgericht; once filed, it reaches us on the normal cycle.
Removing personal data
Natural persons named in the register can object to their data being published here. Requests go to datenschutz@registercheck.de and are handled under the GDPR. A suppressed person's records stop being served through the API; you are responsible for removing any copy you have already stored.