Help
Support
How to contact the Compense developer team, what information to include and what you should never send.
On this page
Channels #
| Channel | What it’s for |
|---|---|
| developers@compense.co | Integration questions, API or SDK errors, keys and technical onboarding. |
| Your Compense account executive | Contracts, active modules, production keys and rate limits. |
| User guides | How to operate the platform from the dashboard and the apps (for advisors and operators). |
What to include in your message #
- The
trace_idof the error (or the response’sX-Request-IDheader). - The operation (
operationIdor method and path) and the approximate time with time zone. - The environment (sandbox, dev or production) and the SDK and version (
compense-sdk-python 1.1.0…). - Your
Idempotency-Keyif it was a write. - The error response body (
problem+json) and, if relevant, the request without sensitive data.
Never send
Your cmp_... key, the whsec_... webhook secret, full identity documents, card numbers or
health data. If a key was exposed by mistake, request its revocation immediately and rotate the
key.
Before you write #
- Check the frequently asked questions and the errors table.
- Reproduce the case in the sandbox if you can: since it’s deterministic, it’s the fastest way for us to see exactly what you see.
- Use
system.health()to confirm your key has the scope.
Reporting an SDK issue #
Tell us the language and version, the method you called, and the expected versus actual result. If you have access to the SDK repository, attach a minimal reproducible case.