Error Handling
What errors to expect and how to build reliable clients around the WatchTower API.
Section
Error shape
WatchTower uses structured API error responses with fields such as error, message, and details.
Section
Common failure classes
Authentication errors
- invalid session
- invalid credentials
- missing API key
- invalid API key
- missing idempotency key
Validation errors
- malformed transaction payload
- invalid status transition
- missing required fields
- invalid token or expired invitation
Authorization errors
- insufficient role
- cross-organization access attempt
Section
Rate limiting
Machine-to-machine ingestion may be limited per organization. Console authentication is also protected against brute-force abuse.
Section
Client recommendations
- always log the response body for non-2xx responses
- use idempotency keys for ingestion retries
- distinguish retryable network failures from validation failures
- avoid retry loops for malformed payloads
Next UpSLA
Continue Through The DocsWatchTower Integration Guides