Guides

Error Handling

Understand Deepvue API error codes, HTTP status codes, and how to handle common errors in your integration.

{
  "detail": "Inactive client_id"
}

Overview

Deepvue APIs return standard HTTP status codes to indicate the success or failure of requests. Error responses include a detail field with a human-readable message describing the issue.

HTTP status codes

Status Code	Meaning	Description
`200`	OK	Request completed successfully
`400`	Bad Request	Invalid request parameters or inactive client
`401`	Unauthorized	Authentication failed or missing credentials
`403`	Forbidden	Valid credentials but insufficient access
`422`	Validation Error	Request parameters failed validation
`429`	Too Many Requests	Rate limit exceeded — slow down and retry
`500`	Internal Server Error	Server-side issue — retry or contact support
`503`	Service Unavailable	Upstream data source is temporarily unavailable

Error response format

Error responses include a detail field explaining the issue:

Common errors and solutions

Your client_id is inactive, disabled, or the request is malformed.

Common messages: "Inactive client_id", "Bad Request"

Verify your credentials in the Deepvue Dashboard
Check if your account is active and in good standing
Ensure the request body and query parameters are correctly formatted
Contact support if the issue persists

Best practices

Always check the HTTP status code before parsing the response body
Implement retry logic with exponential backoff for 500 and 503 errors
Log the transaction_id from successful responses for debugging and support requests
Monitor your API usage through the dashboard's logging section
Handle token expiration gracefully by refreshing before the 24-hour window expires

Was this page helpful?

Built with Documentation.AI

Last updated 1 day ago