Resources
Support
This page lists the ways to reach Tomba and the details that let support resolve an API issue on the first reply.
Get help
| Channel | Use it for |
|---|---|
| Help center | Guides and answers to common account questions |
| Contact form | Account, billing, and API questions; sales and Enterprise |
| support@tomba.io | API and integration issues, and reports of misuse |
| security@tomba.io | Security vulnerabilities. See Security |
| privacy@tomba.io | Data removal and privacy rights requests |
| Status page | Incidents and outages |
What to include
- The
X-Request-IDheader from the response. Every API response carries one. - The time of the request, in UTC.
- The endpoint and its parameters. Leave out personal data such as email addresses where the issue reproduces without it.
- The name or ID of the API key you used. Never send the secret or the full key.
- The error
typeandmessagefrom the response body. See Errors.
Support by plan
| Plan | Support |
|---|---|
| All plans | Email support |
| Growth and up | Priority support with faster response times |
| Enterprise | A named account manager and a custom SLA agreed under contract |
A 99.9% uptime SLA is available only as part of an Enterprise contract. Without a signed SLA, the API has no uptime commitment. Tomba Enterprise lists what the plan includes; to discuss it, use the contact form.
Service status
Check status.tomba.io for open incidents before you report an outage.
Before you contact us
- Errors: what each error type means and how to handle it.
- Rate limits: what a
429response means and how to retry. - Credits and usage: quotas, credit costs, and duplicate requests.
- FAQs
- Changelog: recent changes to the API.
Last modified on