Developers
Developer support
Write to us
| Topic | Address |
|---|---|
| Technical help, API error, documentation question | [email protected] |
| Integration project (software vendor, integrator, financial institution), sandbox access | [email protected] |
| Vulnerability report | [email protected] |
Answers on working days.
What to include
- The response's
request_id(X-Request-Idheader, also present in the error body). - The date and time (UTC), the method and path called, the error
code. - The application's public identifier (
tc_live_…).
Never include an application secret, an access token, a webhook secret or personal data: we do not need them to diagnose.
Diagnostics from the application
A company administrator sees, in Data & integrations › Diagnostics & support, the module status, the background workers' heartbeat, the latest exports, failing webhook deliveries and call volumes; in Connected apps, each application's usage and latest calls.
Security
Report any vulnerability to [email protected], without making it public before a fix and without accessing other people's data. Intrusive tests against production are not allowed; the sandbox will serve such tests once it exists.