Support and contact
Stuck or something isn't working as expected? We can help. Before you reach out, gather a few details — they help us resolve the issue much faster.
Before you write
Collect basic diagnostic data:
correlation_idfrom the error — the most important piece. Every error response includes acorrelation_id; include it in your ticket so we can immediately locate the event context.- What happened and when — a short description, timestamp, and the order or call identifier involved.
- Steps to reproduce — what you did and what you expected.
Never send API keys or secrets in a support ticket. For diagnostics, correlation_id is enough — keys in examples always remain masked (cba_test_••••••••).
How to contact us
Reach the support team through the dashboard — you can open a ticket in the context of your account without manually providing identification data. Final channels and response times will be confirmed at service launch.
Service status
If you suspect a broader outage, check the service status page (we will publish it at launch). Before reporting an incident as an outage, verify that it isn't a connector configuration issue — the connector diagnostics in the dashboard are often helpful here.
Documentation feedback
Found an error or gap in this documentation? Use the rating button at the bottom of each page — it's the fastest way for us to improve the content. Answers to frequently asked questions are also in the Help Center.