Overview
The InstaView API uses standard HTTP status codes and returns structured error responses to help you diagnose and handle issues in your integration.Response Structure
Whether a call succeeded is carried by the HTTP status code, not by a field in the body. Read the status first, then the body.Success Response
The body is the resource. There is no wrapper around it:Error Response
A 4xx or 5xx answers with a flat error object:errors array holding the individual problems — a failed
validation lists one entry per rejected field, and an invalid conversation flow lists one
entry per bad block, each with the path of the block it is on:
Every response also carries an
x-trace-id header holding the same trace id as the body’s
traceId. Quote it when contacting support — it is the fastest way for us to find the
exact request. It is present on success responses too, which have no body field for it.HTTP Status Codes
- 2xx Success
- 4xx Client Errors
- 5xx Server Errors
Error Codes
Authentication Errors
401
The provided API key is invalid, revoked, or expiredSolutions:
- Verify API key format
- Check if key was revoked in dashboard
- Ensure key hasn’t expired
401
The API key has been temporarily suspendedSolution: Contact support or check dashboard for details
Permission Errors
403
API key lacks required scopeSolution: Add required scope to API key or create new key
403
Resource belongs to different companySolutions:
- Verify resource belongs to your company
- Check if using correct companyId (ATS keys)
- Ensure resource hasn’t been deleted
Validation Errors
400
Request validation failedSolution: Fix validation errors in request body
400
Required field not provided
Resource Errors
404
Requested resource doesn’t exist
409
Resource already exists or state conflict
Rate Limiting
429
Too many requestsSolution: Wait for
retryAfter seconds, implement exponential backoffBusiness Logic Errors
403
Company billing limit reachedSolution: Upgrade plan or wait for monthly reset
422
Invalid resource state change
Error Handling Patterns
Basic Error Handling
Comprehensive Error Handler
Retry with Exponential Backoff
Validation Error Handling
Handle field-level validation errors:Idempotency
Implement idempotency for safe retries:Logging and Monitoring
Log errors for debugging and monitoring:Best Practices
Always Check the Status Code
Always Check the Status Code
Provide Context in Errors
Provide Context in Errors
Don't Expose Sensitive Data
Don't Expose Sensitive Data
Implement Circuit Breakers
Implement Circuit Breakers
Next Steps
Rate Limiting
Handle rate limits properly
Best Practices
Production-ready patterns
Authentication
Fix authentication errors
API Reference
See all error codes per endpoint