Skip to main content

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:
List endpoints return a page object instead — see Pagination.

Error Response

A 4xx or 5xx answers with a flat error object:
Some 4xx responses add an 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

Error Codes

Authentication Errors

401
The provided API key is invalid, revoked, or expired
Solutions:
  • Verify API key format
  • Check if key was revoked in dashboard
  • Ensure key hasn’t expired
401
The API key has been temporarily suspended
Solution: Contact support or check dashboard for details

Permission Errors

403
API key lacks required scope
Solution: Add required scope to API key or create new key
403
Resource belongs to different company
Solutions:
  • Verify resource belongs to your company
  • Check if using correct companyId (ATS keys)
  • Ensure resource hasn’t been deleted

Validation Errors

400
Request validation failed
Solution: 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 requests
Solution: Wait for retryAfter seconds, implement exponential backoff

Business Logic Errors

403
Company billing limit reached
Solution: 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

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