Troubleshooting•7 min • Troubleshooting
Troubleshooting IngestAPI and Event API errors
Common causes of 4xx and 5xx errors when sending data into TG2G, and how to fix them.
troubleshootingingestevent-api
Updated recently
4xx client errors
Most 4xx responses indicate an issue with your request: - **401 / 403** – missing or invalid API key header. - **400** – malformed JSON or missing required fields such as `summary` or `logs`. - **429** – you are sending requests faster than your current rate limit.
5xx server errors
- Rare, usually transient issues on our side.
- Implement retries with backoff in your pipelines.
- If errors persist for more than a few minutes, contact TG2G support with timestamps and request IDs if available.