Get Help
Developer questions go to one place: support.revenexx.com. Wherever these docs say "open a support request" or "quote it in a support ticket", that is the destination — there is no separate developer queue and no email address to remember.
Before you open a request
Two checks that regularly save the round trip:
- status.revenexx.com — whether the thing that just failed is failing for everyone. An incident on the status page is already being worked; it does not need a support request.
- The error response itself — gateway errors carry a machine-readable
codeand anerrortext written to be read. Errors explains the format and what each status means, and Debug a failed request walks from the response to its cause.
What to include
A request that can be answered in one round trip carries:
- The
X-Request-IDof a failing request. It is what turns "it failed at 14:20" into a request we can actually trace. A refusal from the gateway itself does not echo one back, so send your own and quote that. See Request IDs. - The tenant slug you sent in
X-Revenexx-Tenant. - The endpoint, the method, and the timestamp — in UTC, not "this morning".
- What you expected and what you got — the actual response status and body, not a paraphrase of them.
A request without these is not rejected. It just starts with the questions above instead of with an answer.
What to expect back
Response times depend on your plan and on the priority of the request. They are set in the terms (§ 21 and Annex 4), which are in German, and this page does not restate them. A complete request — the list above — is what gets a first reply that resolves something rather than asks for the request ID.
Product support or docs feedback
The two channels fix different things, and mixing them up slows both down:
| You found | Where it goes |
|---|---|
| An API that misbehaves, a blocked request, a question the docs don't answer | support.revenexx.com |
| A page that is wrong, unclear, or missing something | The "Was this page helpful?" control at the bottom of that page |
| Several things failing at once | status.revenexx.com — check before filing anything |
The page feedback control opens a prefilled GitHub issue that names the page, and the docs team works from those issues. It is how a docs defect gets fixed — and it is the wrong place for a production problem, because nobody triages an outage from a docs issue.