Tax Genius · India
API Errors & Troubleshooting
Troubleshoot common B2B API authentication, permission, validation, token, application and connectivity errors.
Errors and troubleshooting
Identify documented authentication, permission, application-mapping and payment-token errors, then build safe recovery paths.
Documented error families
- 401 Unauthorized — Invalid API Key or Secret: check protected environment configuration.
- 403 Forbidden — Vendor account suspended: contact the partner team.
- 403 Forbidden — Requested service not enabled: request activation.
- 404 Not Found — Tracking ID not associated with this vendor or unknown.
- 400 Bad Request — Required filing or registration values missing.
- 400 Bad Request — Payment token invalid or expired; obtain an approved replacement.
Safe client error handling
- Do not return API secret or taxpayer information in error screens.
- Record a partner correlation ID and non-sensitive request context.
- Never retry payment or filing mutations blindly; first reconcile application state.
- Treat 400 validation errors as corrective actions, not transient failures.
- Apply bounded backoff only where the backend documents retry-safe operations.
Unspecified operational behaviours
The guide does not define rate-limit thresholds, retry-after headers, idempotency-key header support, or all possible HTTP response shapes. Do not fabricate a production SLA or generic retry guarantee.
Confirm rate limits, deduplication semantics, timeout rules and 5xx response contracts with the FastAPI implementation.